[argh, forgot something]
Carsten Neumann wrote:
> The VRML interpolators are derived from AnimChannel and to use them
> Animation and AnimBlender are simply dropped from the picture. In other
> words the Animation, AnimChannel, AnimBlender part becomes a sort of
> black box that does what I need, while remaining optional for simpler
> situations.
the VRML stuff is not quite working in the patch because I could not
quite figure out how to make the VRML loader understand that the fields
involved in routes have slightly different names in OpenSG than in VRML.
I suspect an appropriate VRMLNodeHelper type implementing mapFieldname()
should do the trick, but could not quite figure out how that is supposed
to work (its only really implemented for one type). Essentially the
question is how do I tell the VRML loader that a VRML route from
container "Foo" field "fieldSomething" should really use a connector
from field "fieldSomeOtherThing" (and the same for the destination field) ?
Thanks,
Carsten
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
