SOMFNAME(3iv)
πΈ SoMFName β the multiple-value field that holds ALL the names π
okay bestie, welcome to SoMFName(3IV) β yes that's the manual page name, we're not copying the whole header line, we're just vibing with it up here at the top π
β¨ NAME β¨
SoMFName β a multiple-value field containing any number of names π¦
𧬠INHERITS FROM
SoField > SoMField > SoMFName
(it's giving legacy, it's giving dynasty, it's giving family tree π)
π SYNOPSIS π
#include <Inventor/fields/SoMFName.h>
π« Methods from class SoMFName
void setValues(int start, int num, const char *strings[])
void setValue(const char *string)
static SoType getClassTypeId()
virtual void getTypeId() const
const SbName & operator [](int i) const
const SbName * getValues(int start) const
int find(const SbName & targetValue, SbBool addIfNotFound
= FALSE)
void setValues(int start, int num, const SbName *newValues)
void set1Value(int index, const SbName & newValue)
const SbName & operator=(const SbName & newValue)
void setValue(const SbName & newValue)
int operator ==(const SoMFName &f) const
int operator !=(const SoMFName &f) const
SbName * startEditing()
void finishEditing()
π« Methods from class SoMField
int getNum() const
void setNum(int num)
virtual void deleteValues(int start, int num = -1)
virtual void insertSpace(int start, int num)
SbBool set1(int index, const char *valueString)
void get1(int index, SbString &valueString)
π« Methods from class SoField
void setIgnored(SbBool ignore)
SbBool isIgnored() const
SbBool isDefault() const
virtual SbBool isOfType(SoType type) const
SbBool set(const char *valueString)
void get(SbString &valueString)
void touch()
SbBool connectFrom(SoField *fromField)
SbBool connectFrom(SoEngineOutput *fromEngine)
void disconnect()
SbBool isConnected() const
SbBool isConnectedFromField() const
SbBool getConnectedField(SoField *&writingField) const
SbBool isConnectedFromEngine() const
SbBool getConnectedEngine(SoEngineOutput *&engineOutput)
const
void enableConnection(SbBool flag)
SbBool isConnectionEnabled() const
int getForwardConnections(SoFieldList &list) const
SoFieldContainer * getContainer() const
π DESCRIPTION π
So picture this: a multiple-valued field that can hold any number of names. Names are these short little series of characters that people generally use for labels or names, and they get stored in a special table designed to allow fast lookup and comparison β like a VIP list at the club, but for characters β¨
ngl, for most purposes an SoMFString field is probably more appropriate. just saying π«Ά
SoMFNames get written to file as one or more strings of characters. Here's the rule, no cap: names must begin with an underscore or an alphabetic character, and must consist entirely of underscores, alphabetic characters, or numbers.
When more than one value is present, all of the values are enclosed in square brackets and separated by commas β for example:
[ Fred, Wilma, _Part_01, translationField ]
it's giving Flintstones meets field system, iconic honestly π
π οΈ METHODS π οΈ
void setValues(int start, int num, const char *strings[])β setsnumvalues beginning at indexstartto the names contained in the given set of character strings.void setValue(const char *string)β sets this field to contain one and only one value, given bystring. monogamy era πstatic SoType getClassTypeId()andvirtual void getTypeId() constβ returns the type for this class, or for a particular object of this class.const SbName & operator [](int i) constβ returns thei'th value of the field.
β οΈ bestie, indexing past the end of the field (passing inigreater thangetNum()) will return garbage. not the cute kind. π
const SbName * getValues(int start) constβ returns a pointer into the array of values in the field, starting at indexstart. The values are read-only; see thestartEditing()/finishEditing()methods for a way of modifying values in place.int find(const SbName & targetValue, SbBool addIfNotFound = FALSE)β finds the given value in the array and returns the index of that value in the array. If the value is not found,-1is returned. IfaddIfNotFoundis set, thentargetValueis added to the end of the array β but-1is still returned. yes really. it adds it and then tells you it didn't find it. make it make sense πvoid setValues(int start, int num, const SbName *newValues)β setsnumvalues starting at indexstartto the values innewValues. The array will automatically be made larger to accommodate the new values, if necessary. glow-up, but for arrays β¨void set1Value(int index, const SbName & newValue)β sets theindex'th value in the array tonewValue. The array will be automatically expanded, if necessary.const SbName & operator=(const SbName & newValue)andvoid setValue(const SbName & newValue)β sets the first value in the array tonewValue, and deletes the second and subsequent values. ruthless. periodt πint operator ==(const SoMFName &f) constandint operator !=(const SoMFName &f) constβ returnsTRUEif all of the values of this field equal (do not equal) those of the given field. If the fields are different types,FALSEwill always be returned β even if one field is anSoMFFloatwith one value of1.0and the other is anSoMFIntwith a value of1, for example. type is not a vibe, it's a boundary πSbName * startEditing()andvoid finishEditing()βstartEditing()returns a pointer to the internally-maintained array that can be modified. The values in the array may be changed, but values cannot be added or removed.
π¨ It is illegal to call any other editing methods betweenstartEditing()andfinishEditing()(e.g.set1Value(),setValue(), etc). do not test this. it will not go well. π
Fields, engines or sensors connected to this field and sensors are not notified that this field has changed until finishEditing() is called. Calling finishEditing() always sets the isDefault() flag to FALSE and informs engines and sensors that the field changed β even if none of the values actually were changed. so it's out here announcing a change that never happened. main character energy fr fr π
and that's the whole page bestie!! this was SoMFName(3IV)(), the one and only, and yes the footer is literally just SoMFName(3IV)() again β it said its own name twice and honestly? relatable. slay, go forth, and may your names always start with an underscore or an alphabetic character π¦ππ
π¦ where this page comes from
- debian bookworm: inventor-doc 2.1.5-10+dfsg-2 Β· LGPL-2.0-or-later
- debian trixie: inventor-doc 2.1.6+ds-2 Β· LGPL-2.0-or-later
- ubuntu jammy: inventor-doc 2.1.5-10-24
- ubuntu noble: inventor-doc 2.1.5-10+dfsg-2.1build2 Β· LGPL-2.0-or-later
- ubuntu questing: inventor-doc 2.1.6+ds-2
- ubuntu resolute: inventor-doc 2.1.6.1+ds-1 Β· LGPL-2.0-or-later
- ubuntu stonking: inventor-doc 2.1.6.1+ds-1 Β· LGPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms