On Sunday 21 April 2002 23:50, Denis Oliver Kropp wrote: > sorry for the late answer, I'll propably need a 'deferred-reply-reminder'.
No problem, better a late answer than no answer :-) > You can attach the event buffer to the window and to the remote control > input device. You will get DFBWindowEvents and DFBInputEvents then. > > So you could simply ignore the DFBWindowEvents that contain key presses > and use the DFBInputEvents from the remote control as key input. There I have the problem, that I need to get events into gtk. The gdk-directfb layer let only events pass which are related to windows. At least I've got this impression when I checked this and by reading the code. Therefore I'm not able to manage the keyboard related focus by myself (grab_keyboard doesn't work). With X this looks different. As far as I remeber I was able to grab the keyboard in X. Is there a reason that keyboard grabbing doesn't work. If not then I could try to make a patch. Perhaps you can give me a hint where to fix that. > You may decide to drop the raw input events when non of your windows > has the focus. This is also interesting. When I create a window and the mouse pointer (which I'm not using) is outside of that window, I get absolutely no event from keyboard into that gdk window. The only solution I found was to create a dummy gdk window which fills the whole screen to make sure I get events. Then when I use gdk_keyboard_grab I can manage that the events flow into the right window, i.e. with the background window I make sure to get events into gdk-directfb and with gdk_keyboard_grab I specify which gdk window should get the events. With simple focus handling this didn't work. And, as I wrote above, without the dummy window I could lose all events when the window was not touched by the mouse pointer (which I don't want to move,because I'm using the keyboard/lirc; but I have attached a mouse, because some directfb application didn't run without). > If you need to prohibit remote control events for windows at all you should > wait until cooperative levels for input devices are introduced. The idea is > to only have input devices connected to the window stack that are not > exclusively accessed by an application. This sounds good and is conform to what I did to solve the problem. I badly hacked the directfb code, that the window doesn't open input devices at all. To summarize: The cooperative levels for input devices would help me alot. More nice would it be to get a better event handling in conjunction with gdk-directfb. Mike -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe directfb-users" as subject.
