Robert, Heh. I wondered if that was the reason that previous plugin writers had made such efforts to avoid it (although the OpenFlight loader seems to use it - is that a different case)?
but the way > to tackle is to create an options object that packs this variables > together and then you just pass a reference to to object Can you point me at an example in the plugins? While I'm here, I didn't like the way that options had to be passed as strings - it seemed ugly. Is there a better way of defining this - e.g. a plugin independent way, by extending osg::Options or something? I intend to apply the same sort of functionality to the 3DS loader, and it would be good to be consistent... David
_______________________________________________ osg-submissions mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
