Hi Philip, On Tue, May 26, 2009 at 12:19 PM, Philip Lamb <[email protected]> wrote: > Is the Present3D application you're referring to one that I could look at? > It seems to me that as it stands, AnimationPath has some bugs, and if these > have to be corrected while not breaking existing work-arounds in use, it > would be useful to be able to test against them.
Present3D is now checked into as part of the core OSG svn/trunk. You can find it in applications/present3D. >> One thing that Present3D does do is when it does the reset >> it does an update on the node - the code is: >> >> apc->reset(); >> apc->update(*_node); >> > > I can't see how this could possibly work, since apc->reset() sets _firstTime > to DBL_MAX, and then apc->update() internally queries getAnimationTime() > which uses the DBL_MAX value as if it was a legitimate value in the equation > (_latestTime - _firstTime). This could only produce a random very large > negative number, which might have the effect of being prior to the > animation, but certainly incorrect. I'll put some debugging code into and see how it's working. Perhaps it's only working by fluke right now. > BTW, if this isn't the correct place to discuss submissions, let me know. It's the correct place to discuss submissions, but if it open out into a more general topic duscussion then it'd be best to move it to osg-users. In this case I've tested your submission and found that it breaks things so for now it's rejected. Seeking a solution might be best done on osg-users. Do you have a small code segment that is able to reproduce the problems you are seeing? Robert. _______________________________________________ osg-submissions mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
