other apps can't get input

SuperElectric

07-02-2006 22:02:56

I'm finding it impossible to use my IDE's debugger to debug my pyogre app, because the app seems to hijack my keyboard and mouse input. The debugger will come to the fore when a breakpoint is hit, but I can't interact with it. Worse, I can't alt-tab to a terminal to kill the ogre app, so the best I can do at that point is three-finger-salute the X server.

Is there a way to get FrameListener to not eat mouse/keyboard events so that other apps can use them?

Also, is there a way to keep the mouse pointer from hiding when the ogre app launches? There's a tutorial on how to make the cursor visible using CEGUI, but I'm hoping there's a simpler solution; I just want to see where it is for debugging purposes.

-- Matt

griminventions

08-02-2006 15:09:43

All those things are under the control and discretion of Ogre's input system. You can use a different input system (PyGame/SDL?) to work around it, I'd say.

pjcast

08-02-2006 17:13:53

You could try the Pyhton bindings for OIS.. OIS alows you to set the cooperative modes of DX. http://www.sourceforge.net/projects/wgois .. the oisaddons/python module and main ois module.

bigjhnny

19-03-2006 22:22:46

You could try the Pyhton bindings for OIS.. OIS alows you to set the cooperative modes of DX. http://www.sourceforge.net/projects/wgois .. the oisaddons/python module and main ois module.

Could you provide further instructions on how to obtain the python module for OIS?

OGRE cvs never works for me. The windows zip on the OIS home page doesn't contain oisaddons....

Dead end for me right now.

pjcast

20-03-2006 01:15:37

OIS has its own sourceforge page. http://www.sourceforge.net/projects/wgois

If you can't access "oisaddons" cvs module in ois's cvs let me know at my forums (as I check those more often then here) and I'll get a oisaddons source zip uploaded.

pjcast

20-03-2006 16:00:24

Ok, I went ahead and added the latest source of oisaddons to my downloads page of my site. With OIS, you can easily set the mouse to non_exclusive in win32 and no grabbing in X windows (so that it is free) - only thing is, when not grabbed in X windows, once out of the window bounds you will get no more move/click messages.

However, the best thing for debugging on X is to have a way to ssh (or telnet depending on your tastes) into your box to kill any non responsive apps.