Hi Gianni, On 24 October 2014 10:48, Gianni Ambrosio <[email protected]> wrote:
> Honestrly I'm not sure this is just a matter of Qt code. I can get the > mouse event on the Qt side and let OSG code handlling it later. I debugged > that code and the mouse event seems correctly added to the osg event queue > but calling eventTraversal() the event is not processed. I guess the event > is processed in a frame() call, but removing the event handler too early > (in mouseReleaseEvent()) it causes the behaviour I experienced. That's why > I asked if there is a way to force event processing in pure OSG code. > There really is too little to go on for a 3rd party to know what might be going on, what is correct and what might not be. You have all the code in front of you, I and others don't, there are really limits to our ability to onimpotent. As for forcing event processing in pure OSG code. Well you can create an event and pass it directly to the event handling/callback. Robert
_______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
