Antonio Bleile wrote: > Scrive Marcus Lindblom <[EMAIL PROTECTED]>: > >> Inspecting the change list seems like the easy way, if it's possible and >> fits your application. > > That's interesting! The problem is that I don't really know > how to interpret the change list. When I call > Thread::getCurrent()->getChangeList()->dump(); > I get some interesting output, e.g. the from/to/up changes > of the camera. But I need to know which object has changed, > and as far as I can see the changelist holds just the field > containers, not the nodeptr's to which the fields belong?
Right. But you should get the fieldcontainers (cores/nodes/etc) whose fields have been changed too. Presumably by ID or something. > In case the camera has been rotated I don't need to update > the shadows, so a binary test on the changelist empty state > wouldn't be sufficient... :( Hm. I don't know how your app is structured, or who changes the scene. Assuming you have _no_ info, other than "render this scene, which might've changed", it does't seem easy. :-/ Writing a parser for the dump-format might be too tricky. It ought to be possible to àccess the list directly (at least as read-only). What do the core-devs have to say? Cheers, /Marcus ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Opensg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
