Is there an equivalent function to the Performer
pfObject::getNamedUserDataSlot? Our code uses it a lot to store object data.
I'm guessing we could just store the data in a map and uses the slot id
returned as a key.
Tony V
--
Read this topic online her
Hi Tony,
you have two options:
- osg::Object:get/setUserData
- osg::Object:setUserValue (for this one you have to #include
Nick
On Thu, Sep 10, 2015 at 7:56 AM, Tony Vasile wrote:
> Is there an equivalent function to the Performer
> pfObject::getNamedUserDataSlot? Our code uses it a lot to s
Hi Tony,
As Nick says there is the Node::setUserValue(..) template method and
Node::setUserData(). When you use UserValue it creates a UserDataContainer
to hold the values in a vector of osg::Object*, so this UserDataContainer
kinda has "slots". The UserDataContainer is only created on demand an
Hi Nick & Robert,
That's not quite the same functionality as it appears that in Performer
there is some sort of memory/map that is used to map a user defined name as a
string to a slot number. You then add data to the node using this slot number.
Performer does have a call to setUserData whic
Hi Tony,
Spend some time with OSG code, you'll find it far more flexible than
anything that Performer had. It's investing time into learning the OSG
rather than just working out how to do something equivalent to Performer
because your original design may well have been compromised by the
limitati
Unfortunately we have a tight schedule to do this port. The usual 6 months of
work in 4 months type of affair. Thanks for the advice.
Tony V
--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=65091#65091
_
Hi Tony,
On 10 September 2015 at 09:30, Tony Vasile wrote:
> Unfortunately we have a tight schedule to do this port. The usual 6 months
> of work in 4 months type of affair. Thanks for the advice.
>
I can sympathise with impossible tight schedules, my point still stands
though. The OSG isn't P
I have looked at ValueObject and was wondering why there is no option to save
an osg::Object or an osg::Referenced object. Is this an omission or intended?
Tony V
--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=65736#65736
Hi Tony,
On 22 November 2015 at 23:16, Tony Vasile wrote:
> I have looked at ValueObject and was wondering why there is no option to
> save an osg::Object or an osg::Referenced object. Is this an omission or
> intended?
>
I don't know where you got this impression. You can save custom
osg::Obje
Hi Robert,
Unless I am going blind I couldn't see an explicit apply for osg::Object in
either GetValueVisitor or SetValueVisitor, hence the question.
Tony V
--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=65750#65750
On 23 November 2015 at 11:38, Tony Vasile wrote:
> Hi Robert,
> Unless I am going blind I couldn't see an explicit apply for
> osg::Object in either GetValueVisitor or SetValueVisitor, hence the
> question.
This is different question to saving data, the serialization support uses
completely d
Hi Robert,
We are trying to save classes which have more than simple types or the list
specified in ValueObject. If we try and save an object which has osg::Object
has its parent then you get a linker error about missing apply routines for
SetValueVisitor and GetValueVisitor. I have worked ar
Hi Tony,
The name of the osg::Object is used as a key in UserDataContainerL see the
methods:
/** Get the index position of first user data object that matches
specified name.*/
virtual unsigned int getUserObjectIndex(const std::string& name,
unsigned int startPos=0) const = 0;
13 matches
Mail list logo