Hi Art,
On Wed, Dec 17, 2008 at 11:33 AM, Art Tevs wrote:
> yes we could also add some kind of getName() which returns a string. However
> using a hash based approach would have more performance, because only integer
> comparison is needed (if you want to check for the visitor type during a
>
VisitorType enum which
isn't really covers the whole bunch of visitor types.
cheers,
art
--- Robert Osfield schrieb am Mi, 17.12.2008:
> Von: Robert Osfield
> Betreff: Re: [osg-users] Unknown visitor running first and general visitor
> types
> An: stud_in...@yahoo.de, &quo
Hi Art,
All osg::Object's have a className() method. NodeVisitor is just
subclass from osg::Referenced so doesn't have this, but we could
certainly add it, it'd be less effort and more informative than the
coming up with some hashmap scheme.
Robert.
On Wed, Dec 17, 2008 at 10:30 AM, Art Tevs w
Sorry, I have send the message before completing it:
unsigned int osg::computeVisitorType(const std::string& type_id)
{
return some_hash(type_id);
}
This would enable the possibility to check out which type of visitor is
currently traversing the node. Also in future releases or in external
a
Hi folks,
It seems that in the current version of osg, there is some unknown node visitor
running over all of my nodes. The node type does return just NODE_VISITOR=0.
Hence I do not see any way to find out, which type of visitor is traversing
there.
Currently there exists so many different nod
5 matches
Mail list logo