Hi,
most subclasses of SceneGraphObject have a set of capability bits and a corresponding set of capabilityIsFrequent bits. Capability bits control if a particular attribute of a node or node component is readable or writable within a live or compiled scene graph for performance reasons.
Only one capability or capabilityIsFrequent bit may be set or cleared per method invocation (see SceneGraphObject javadoc). These bits (integers) cannot be 'ORed' together, because they are numbered consecutively.
For each concerned class the capability bits can be considered as an unique bit position within a long number (64 bit). That's the way Java 3D stores them internally, but these 'longs' are not public.
Here are some relevant figures (without guarantee):
- min cap bit: 0 / Node.ENABLE_COLLISION_REPORTING
- max cap bit: 47 / Node.ALLOW_LOCAL_READ
- most cap bits: 43 / ConeSound (all set: 212205744160763L)
- caps are defined in 59 classes
- caps are to be set/cleared in 83 non abstract classes
- total cap bits: 356
For a X3D-Shape/Model-Loader that supports Java 3D extensions capability bits are represented by its long number to avoid massive text import/export (coming soon).
A tool and a source code snippet are now available in advance. They allow to calculate these 'longs' respectively to set and clear the bits in a convenient way. If your Java 3D application might benefit from it, feel free to download CapBitSelector (FreeWare):
http://www.interactivemesh.org/freeware/capbitselector.htmlPlease, be aware that a 'long' alone doesn't tell you to which class it belongs or doesn't let you imagine which bits are set or cleared.
August
[Message sent by forum member 'interactivemesh' (interactivemesh)]
http://forums.java.net/jive/thread.jspa?messageID=261594---------------------------------------------------------------------
To unsubscribe, e-mail:
interest-unsubscribe@...
For additional commands, e-mail:
interest-help@...
