[osg-users] animation synchronisation

[Jason Beverage]

Hi Robert,

This documentation improbability drive sounds really useful, but we really
need better documentation on it;)

Jason

On Mon, Mar 3, 2008 at 4:15 AM, Robert Osfield <robert.osfield at gmail.com>
wrote:

> On Sun, Mar 2, 2008 at 8:51 PM,  <dkfm4 at gmx.net> wrote:
> > Hello!
> >
> >  How can/should I synchronize the application flow-control to the end of
> >  an animation (realized as osg::AnimationPath) ?
> >
> >  Assume: we have a projectile that should be animated.
> >  1. we calculate the trajectory and setup the animation-path with some
> trajectory data.
> >  2. then the animation-path will be applied to the projectile-node (the
> >  exact way to do this, is still vague to me; the only information source
> >  I found untill now, is the osganimation example, which handles only a
> >  single animation type, with endless animation)
> >
> >  3. == now: how can I sync the rest of the application with the end of
> the
> >  projectile-animation ? ==
> >  e.g. expand scene graph with new data, start other animation(s), etc...
>
> There isn't a built in feature to do this - the OSG can't provide all
> the features that all users might require, so rather than chase this
> impossible task the extensibility is what saves the day.   In this
> light, try subclassing from the AnimationPathCallback and add your own
> monitor and catch code.   Or perhaps just decorated the
> AnimationPathCallback with your own callback that nests it.
>
> >  The way with polling the timer seems somehow crude to me... There
> should
> >  be a better way ?! (better documentation !)
>
> What better documentation for solving tasks that haven't been foreseen
> as features that users may wish?
>
> What we really need is a documentation improbability drive, one that
> is able to read minds and foresee the future and the document it
> fully, with full diagrams, and provides example code that exactly
> matches your specific needs, in fact just provides your whole program
> written for you, as if you have written it because the documentation
> improbability drive has copied it from the future - just by copying
> what you wrote in the future means that you have a circular reference,
> and an infinite loop that if you are not careful will spiral in on
> itself creating a time space vortex that sucks in all matter and the
> universe implodes. => POP! <=  ;-)
>
> Since I don't know of a fully functioning documentation improbability
> drive yet we'll just have to stick with question and answers on the
> osg-users mailing list, it's probably the cloest we can get to it, and
> so far it doesn't seem to have swallowed up any universes, umm....
> perhaps I'm unwittingy part of documentation improbability drive and
> if I press send the loop will be completed... ooo dangerous.  Do I
> feel lucky this Monday mornign? Ohh well what will be will be....
>
> Robert ;-)
> Robert.
> _______________________________________________
> osg-users mailing list
> osg-users at lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.openscenegraph.org/pipermail/osg-users-openscenegraph.org/attachments/20080303/13801a82/attachment.htm