Hi Paul, When I original introduced FrameStamp I thought ahead and saw that it could be useful to have a calender time available via FrameStamp. For instance an ephemeris model could use it. The use of it being in FrameStamp is that it allows apps to decouple the time they use for simulation purposes from the application implementation.
Right now the calander time ins't populated, and if you want to use it you'd need to populate it yourself. The way I'd implement it in an app would be by overriding Viewer::advance() that updates the FrameStamp. Robert. On Wed, Dec 3, 2008 at 10:26 PM, Paul Martz <[EMAIL PROTECTED]> wrote: > Hi Robert -- There doesn't appear to be any code in the OSG distribution > that sets or gets the calendar time in FrameStamp. Is this purely for > application convenience? Applications can store any values they want in the > tm struct? > > (The header comment says, "Note the calendar time can be an artificial > simulation time or capture the real time of day etc." The comment doesn't go > into detail about how those options are set, but to me the comment seems to > imply that FrameStamp (or something else in OSG) manages calendar time and > can be configured for either of those options. But this is not the case from > the code I've seen, so perhaps I'm misinterpreting it.) > > Paul Martz > Skew Matrix Software LLC > http://www.skew-matrix.com <http://www.skew-matrix.com/> > +1 303 859 9466 > > _______________________________________________ > osg-users mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org > _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
