On Thu, Nov 7, 2013 at 9:40 AM, Deniz Koçak <lend...@gmail.com> wrote:
> It seems that, > thrusting the Qt's Signal/Slot mechanism is not a good option as Jan > pointed. > I think the trouble is that you are expecting it to do something that it isn't meant to do. Perhaps you have confused the "synchronous call" with the idea of "synchronized call" from Java. In Java it does actually mean mutual exclusion on the object and with that semantics your code would have worked. In C++ you could implement something similar with an object-level lock shared between all "synchronized" slots, but I think the performance would be better if you use the buffer and the callback instead - the buffer would be locked for a much shorter time (callback invocation vs. the entire rendering time), decoupling the rendering and GUI. J.
_______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
