Hi Carsten Carsten Neumann schrieb: > Hello Christoph, > > attached version works for me on windows, but since it does not clean > up properly after itself it may crash on exit. > >> Is there any other way to work on the scene graph data within two (or >> more) threads without Ping-Pong-Sync? I think I'll have to face this >> problem ;-) > > it becomes easier if you can set up threads/aspects in a > producer-consumer style where the render thread only picks up changes > but does not modify the scenegraph itself. > From what you described, that would mean you'd have to transfer the > input events to aspect 0 (perhaps setting up a queue, perhaps using > some mechanism built into Qt, not sure what they have there) and > handle them there. > Then all changes to the scene would happen on aspect 0 and you'd just > sync aspect 1 whenever an update is ready. > > Hope it helps, > Carsten > Thanks for the updated example. Luckily I have already operations functionality that can separating execution of ops from the issuing thread. I'll try to switch to the suggested concept this weekend ;-)
Cheers, Christoph ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Opensg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
