NodeCachedReferenceCount
from panda3d.core import NodeCachedReferenceCount
- class NodeCachedReferenceCount
Bases:
Bases:
CachedTypedWritableReferenceCount
This class further specializes
CachedTypedWritableReferenceCount
to also add a node_ref_count, for the purposes of counting the number of times the object is referenced by a “node”, presumably aPandaNode
.This essentially combines the functionality of
NodeReferenceCount
andCachedTypedWritableReferenceCount
, so that a derivative of this object actually has three counters: the standard reference count, the “cache” reference count, and the “node” reference count. Rather than multiply inheriting from the two reference count classes, we inherit only fromCachedTypedWritableReferenceCount
and simply duplicate the functionality ofNodeReferenceCount
, to avoid all of the problems associated with multiple inheritance.The intended design is to use this as a base class for
RenderState
andTransformState
, both of which are held byPandaNodes
, and also have caches which are independently maintained. By keeping track of how many nodes hold a pointer to a particular object, we can classify each object into node-referenced, cache-referenced, or other, which is primarily useful for PStats reporting.As with CachedTypedWritableReferenceCount’s
cache_ref()
andcache_unref()
, the new methodsnode_ref()
andnode_unref()
automatically increment and decrement the primary reference count as well. In this case, however, there does exist a NodePointerTo<> class to maintain thenode_ref()
counters automatically.Inheritance diagram
- static get_class_type() TypeHandle
- get_referenced_bits() int
Returns the union of the values defined in the Referenced enum that represents the various things that appear to be holding a pointer to this object.
If R_node is included, at least one node is holding a pointer; if R_cache is included, at least one cache element is.
- node_ref()
Explicitly increments the reference count.
This function is const, even though it changes the object, because generally fiddling with an object’s reference count isn’t considered part of fiddling with the object. An object might be const in other ways, but we still need to accurately count the number of references to it.