Hi, On Wed, 2012-01-11 at 13:49 +0100, "Christoph Fünfzig" wrote: > Hi, > > coming back to this in the new year .. > My application is running just fine, changing the camera (via Navigators) > and changing the matrix field of some transforms. > But I see inbetween states during changes in dependent aspects > (which synchronize with the application aspect performing them): > > OSG::commitChanges(); > // do camera changes and model transform changes > performNavigation(); > OSG::commitChanges(); > // synchronize with renderer > tile->syncBarrier->enter(config.numPipes()+1); > // sync to renderers > tile->syncBarrier->enter(config.numPipes()+1); > > Could someone hint me to documentation on OSG::commitChanges? > What does it do exactly?
calls changed on the containers that changed since the last commitChanges. It is basically the replacement for the old endEdit, as this was removed for OpenSG 2. The only main difference is that while endEdit worked directly on one container at a time and relied on the user to provide the correct FieldMasks, commitChanges walks through the ChangeList and calls changed on all containers changed since the last commitChanges and it does not rely on user input to get the FieldMask. As in OpenSG 1.x the changed call is/should be used to compute dependent data, that part did not change. kind regards gerrit ------------------------------------------------------------------------------ Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox _______________________________________________ Opensg-users mailing list Opensg-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensg-users
