fields(3)
okay so bestie, this is fields(3) from the Library Functions Manual β section 3 energy, library functions girlies only π«Ά and it's a whole list of classes, so hydrate and let's go π
β¨ NAME β¨
fields β Field Classes, periodt π
π SYNOPSIS π
π¦ Classes π¦
class SoFieldβ the top-level abstract base class for fields. the mother of them all π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 SoMFVec2dβ a container forSbVec2dvectors.class SoMFVec2fβ a container forSbVec2fvectors.class SoMFVec2i32β a container forSbVec2i32vectors.class SoMFVec2sβ a container forSbVec2svectors.class SoMFVec3bβ a container forSbVec3bvectors.class SoMFVec3dβ a container forSbVec3dvectors.class SoMFVec3fβ a container forSbVec3fvectors.class SoMFVec3i32β a container forSbVec3i32vectors.class SoMFVec3sβ a container forSbVec3svectors.class SoMFVec4bβ a container forSbVec4bvectors.class SoMFVec4dβ a container forSbVec4dvectors.class SoMFVec4fβ a container forSbVec4fvectors.class SoMFVec4i32β a container forSbVec4i32vectors.class SoMFVec4sβ a container forSbVec4svectors.class SoMFVec4ubβ a container forSbVec4ubvectors.class SoMFVec4ui32β a container forSbVec4ui32vectors.class SoMFVec4usβ a container forSbVec4usvectors.class SoMFieldβ the base class for fields which can contain multiple values. the many-values queen πclass SoSFBitMaskβ a container for a set of bit flags.class SoSFBoolβ a container for anSbBoolvalue.class SoSFBox2dβ a container for anSbBox2dvector.class SoSFBox2fβ a container for anSbBox2fvector.class SoSFBox2i32β a container for anSbBox2i32vector.class SoSFBox2sβ a container for anSbBox2svector.class SoSFBox3dβ a container for anSbBox3dvector.class SoSFBox3fβ a container for anSbBox3fvector.class SoSFBox3i32β a container for anSbBox3i32vector.class SoSFBox3sβ a container for anSbBox3svector.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. πΈ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β the source says, and I quote, it'svoid"classusedfordetectingfieldchanges.β yes bestie, that's literally how it's written in the original, no I will not be editing it π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 SoSFVec2dβ a container for anSbVec2dvector.class SoSFVec2fβ a container for anSbVec2fvector.class SoSFVec2i32β a container for anSbVec2i32vector.class SoSFVec2sβ a container for anSbVec2svector.class SoSFVec3bβ a container for anSbVec3bvector.class SoSFVec3dβ a container for anSbVec3dvector.class SoSFVec3fβ a container for anSbVec3fvector.class SoSFVec3i32β a container for anSbVec3i32vector.class SoSFVec3sβ a container for anSbVec3svector.class SoSFVec4bβ a container for anSbVec4bvector.class SoSFVec4dβ a container for anSbVec4dvector.class SoSFVec4fβ a container for anSbVec4fvector.class SoSFVec4i32β a container for anSbVec4i32vector.class SoSFVec4sβ a container for anSbVec4svector.class SoSFVec4ubβ a container for anSbVec4ubvector.class SoSFVec4ui32β a container for anSbVec4ui32vector.class SoSFVec4usβ a container for anSbVec4usvector.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 πΈ
so like, fields are the data containers in the scene graph. nodes and engines all use fields to store their public data. that's the whole job, and they do it flawlessly, no cap π«Ά
fields can be inter-connected, which means a change at one location in a scene graph makes other parts of the scene graph automatically get updated too. the way that works: direct field-to-field connections cause values to get duplicated, while field connections together with engines can create whole complex networks for that updating, including mathematical computations and logical operations. and listen β field connections are uni-directional, but if you set up a connection in both directions you get yourself a bi-directional connection. it's giving mutuals π€
fields split into two groups first: "single fields" and "multifields". single-fields contain just one value, while multi-fields can contain many values β or even none at all. iconic range, honestly π
besides the fields that are part of nodes, you also have "global fields". the "realtime" field is one such field.
and the fields in VRML97 nodes have additional semantics, bestie, pay attention: some are "event_in" and some are "event_out", listening for events or triggering events.
β οΈ"event_in"events should not be read from, and"event_out"fields should not be written to. like, do not do it. that's the rule, fr fr π
π AUTHOR π
Generated automatically by Doxygen for Coin from the source code. (so nobody hand-wrote this, it was beamed into existence by a doc generator and honestly, slay π¦)
and that's the whole page, bestie β brought to you by Coin, Version 3.1.3 π go forth and connect some fields π
π¦ where this page comes from
- fedora 43: Coin3-devel 3.1.3-40.fc43 Β· GPL-2.0-only
- fedora 43: Coin3-devel 3.1.3-40.fc43 Β· GPL-2.0-only
- fedora 44: Coin3-devel 3.1.3-42.fc44 Β· GPL-2.0-only
- fedora 44: Coin3-devel 3.1.3-42.fc44 Β· GPL-2.0-only
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms