coin_fields(3)
β¨ NAME β¨
coin_fields β Field Classes π
- The fields are the data containers in the scene graph. Nodes and engines all use fields to store their public data. π
π¦ SYNOPSIS π¦
π Classes π
okay bestie, here's the whole roster, no skips, no cuts, every single one:
class SoFieldβ the top-level abstract base class for fields. the blueprint. the blueprint's blueprint. πclass SoFieldDataβ a container for a prototype set of fields.class SoMFBitMaskβ a container for a set of bitmasks. πclass SoMFBoolβ a container forSbBoolvalues.class SoMFColorβ a container forSbColorvalues. πclass SoMFColorRGBAβ a container forSbColor4fvalues.class SoMFDoubleβ a container for double float precision point values.class SoMFEngineβ a container for engines. π§class SoMFEnumβ a container for a set of enumerated values.class SoMFFloatβ a container for floating point values.class SoMFInt32β a container for 32-bit integer values.class SoMFMatrixβ a container forSbMatrixvalues.class SoMFNameβ a container forSbNamevalues.class SoMFNodeβ a container for nodes.class SoMFPathβ a container for paths.class SoMFPlaneβ a container forSbPlanevalues.class SoMFRotationβ a container forSbRotationvalues.class SoMFShortβ a container for short integer values.class SoMFStringβ a container forSbStringvalues.class SoMFTimeβ a container forSbTimevalues.class SoMFUInt32β a container for 32-bit unsigned integer values.class SoMFUShortβ a container for unsigned short integer values.class SoMFVec2bβ a container forSbVec2bvectors.class SoMFVec2sβ a container forSbVec2svectors.class SoMFVec2i32β a container forSbVec2i32vectors.class SoMFVec2fβ a container forSbVec2fvectors.class SoMFVec2dβ a container forSbVec2dvectors.class SoMFVec3bβ a container forSbVec3bvectors.class SoMFVec3sβ a container forSbVec3svectors.class SoMFVec3i32β a container forSbVec3i32vectors.class SoMFVec3fβ a container forSbVec3fvectors.class SoMFVec3dβ a container forSbVec3dvectors.class SoMFVec4bβ a container forSbVec4bvectors.class SoMFVec4ubβ a container forSbVec4ubvectors.class SoMFVec4sβ a container forSbVec4svectors.class SoMFVec4usβ a container forSbVec4usvectors.class SoMFVec4i32β a container forSbVec4i32vectors.class SoMFVec4ui32β a container forSbVec4ui32vectors.class SoMFVec4fβ a container forSbVec4fvectors.class SoMFVec4dβ a container forSbVec4dvectors.class SoMFieldβ the base class for fields which can contain multiple values. the multiverse of fields. β¨class SoSFBitMaskβ a container for a set of bit flags.class SoSFBoolβ a container for anSbBoolvalue.class SoSFBox2sβ a container for anSbBox2svector.class SoSFBox2i32β a container for anSbBox2i32vector.class SoSFBox2fβ a container for anSbBox2fvector.class SoSFBox2dβ a container for anSbBox2dvector.class SoSFBox3sβ a container for anSbBox3svector.class SoSFBox3i32β a container for anSbBox3i32vector.class SoSFBox3fβ a container for anSbBox3fvector.class SoSFBox3dβ a container for anSbBox3dvector.class SoSFColorβ a container for anSbColorvalue. πΈclass SoSFColorRGBAβ a container for anSbColor4fvalue.class SoSFDoubleβ a container for a double precision floating point value.class SoSFEngineβ a container for a single engine.class SoSFEnumβ a container for an enum value.class SoSFFloatβ a container for a floating point value.class SoSFImageβ used to store pixel images. πΌοΈ (ok no emoji per rules but vibe intact)class SoSFImage3β used to store 3D (volume) images.class SoSFInt32β a container for a 32-bit integer value.class SoSFMatrixβ a container for anSbMatrix.class SoSFNameβ a container for anSbName.class SoSFNodeβ a container for a single node.class SoSFPathβ a container for a single path.class SoSFPlaneβ a container for anSbPlanevalue.class SoSFRotationβ a container for anSbRotation.class SoSFShortβ a container for a short integer value.class SoSFStringβ a container for anSbString.class SoSFTimeβ a container for anSbTimevalue.class SoSFTriggerβ literally justthe void"classusedfordetectingfieldchanges.no notes, that's what it says, that's the whole thing, and honestly? iconic. πclass SoSFUInt32β a container for a 32-bit unsigned integer value.class SoSFUShortβ a container for a unsigned short integer value.class SoSFVec2bβ a container for anSbVec2bvector.class SoSFVec2sβ a container for anSbVec2svector.class SoSFVec2i32β a container for anSbVec2i32vector.class SoSFVec2fβ a container for anSbVec2fvector.class SoSFVec2dβ a container for anSbVec2dvector.class SoSFVec3bβ a container for anSbVec3bvector.class SoSFVec3sβ a container for anSbVec3svector.class SoSFVec3i32β a container for anSbVec3i32vector.class SoSFVec3fβ a container for anSbVec3fvector.class SoSFVec3dβ a container for anSbVec3dvector.class SoSFVec4bβ a container for anSbVec4bvector.class SoSFVec4ubβ a container for anSbVec4ubvector.class SoSFVec4sβ a container for anSbVec4svector.class SoSFVec4usβ a container for anSbVec4usvector.class SoSFVec4i32β a container for anSbVec4i32vector.class SoSFVec4ui32β a container for anSbVec4ui32vector.class SoSFVec4fβ a container for anSbVec4fvector.class SoSFVec4dβ a container for anSbVec4dvector.class SoSFieldβ the base class for fields which contains only a single value. one value, one vibe. πclass SoFieldListβ a container for pointers toSoFieldobjects.
π Detailed Description π
okay so real talk: the fields are the data containers in the scene graph. Nodes and engines all use fields to store their public data. that's the whole point of them. π
Fields can be inter-connected, and that's the fun part β changes at one location in a scene graph cause other parts of the scene graph to automatically also get updated. β¨ Direct field-to-field connections will cause values to get duplicated, while field connections together with engines can create complex networks for such updating that include mathematical computations and logical operations. Field connections are uni-directional, but setting up a connection in both directions will cause a bi-directional connection. yeah. both ways. mutuals. π«Ά
Fields are first divided into two groups: "single fields" and "multifields". Single-fields contain just one value, while multi-fields can contain many values or even none at all. (yes bestie, zero values is a valid amount of values, we support that.) π
Besides fields that are part of nodes, you also have "global fields". The realtime field is one such field. π
The fields in VRML97 nodes have additional semantics. Some are "event_in" and some are "event_out" β listening for events or triggering events, respectively.
β οΈ bestie listen to me: "event_in" events should not be read from, and "event_out" fields should not be written to. that's not a suggestion, that's the rule. don't do it. π
π«Ά Author π«Ά
Generated automatically by Doxygen for Coin from the source code.
and that's the page, bestie!! β¨ this was coin_fields(3), served to you by Coin, Version 4.0.10, dated Thu Jun 25 2026 00:00:00 β yes the whole timestamp, we don't gatekeep dates here. ππ slay, go connect some fields, and remember: uni-directional unless you make it mutual. periodt. ππΈ
π¦ where this page comes from
- fedora 43: Coin4-devel 4.0.10-1.fc43 Β· BSD-3-Clause AND GPL-3.0-or-later
- fedora 43: Coin4-devel 4.0.10-1.fc43 Β· BSD-3-Clause AND GPL-3.0-or-later
- fedora 44: Coin4-devel 4.0.10-1.fc44 Β· BSD-3-Clause AND GPL-3.0-or-later
- fedora 44: Coin4-devel 4.0.10-1.fc44 Β· BSD-3-Clause AND GPL-3.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms