Quoting Mike Pieper ([EMAIL PROTECTED]): > Hi All, > > I need full control over events. My events are all coming from a remote and > my program should decide who gets these events.
Hi, sorry for the late answer, I'll propably need a 'deferred-reply-reminder'. > Now I have a problem with the DirectFB-Windows. When I attach an EventBuffer > to a window than this means that the window will propagate its events into > this event buffer. Is that right? That's right, all window events sent to this window will get into the buffer. > But how can I control which events the window gets? Does the 'window' opens > all input devices? Can I control which input devices are opened by the window? > I need the window events, but _not_ the key press events. The window stacking code attaches to all input devices and does cursor movements whenever axis motion events arrive. Key press/release events are propagated to the focused window. > Any ideas? 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. You may decide to drop the raw input events when non of your windows has the focus. > How to do that in a GTK+ context? I mean there I have no influence on how > windows are created. 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. -- Best regards, Denis Oliver Kropp .------------------------------------------. | DirectFB - Hardware accelerated graphics | | http://www.directfb.org/ | "------------------------------------------" Convergence GmbH -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe directfb-users" as subject.
