And some debug output which occurs for any keypress on my target system. (-) [Keyboard Input 173.930] ( 7482) Core/Input: dfb_input_dispatch( 0x44a8e0, 0x7f1ffc60 ) (-) [Keyboard Input 173.930] ( 7482) Core/Input/Evt: -> (01) KEYPRESS (-) [Keyboard Input 173.931] ( 7482) Core/Input/Evt: -> TIMESTAMP 731997256.732263316 (-) [Keyboard Input 173.931] ( 7482) Core/Input/Evt: -> KEYCODE 111 (-) [Keyboard Input 173.931] ( 7482) Core/Input/Evt: -> KEYID 0xf643 (-) [Keyboard Input 173.931] ( 7482) Core/Input/Evt: -> KEYSYMBOL 0xf002 (-) [Keyboard Input 173.931] ( 7482) Core/Input/Evt: -> MODIFIERS 0xffffffff (-) [Keyboard Input 173.931] ( 7482) Core/Input/Evt: -> LOCKS 0x0001 (-) [Keyboard Input 173.931] ( 7482) Core/Input/Evt: => TIMESTAMP 731997256.732263316 (-) [Keyboard Input 173.932] ( 7482) Core/Input/Evt: => KEYCODE 111 (-) [Keyboard Input 173.932] ( 7482) Core/Input/Evt: => KEYID 0xf643 (-) [Keyboard Input 173.932] ( 7482) Core/Input/Evt: => KEYSYMBOL 0xf002 (-) [Keyboard Input 173.932] ( 7482) Core/Input/Evt: => MODIFIERS 0xffffffff (-) [Keyboard Input 173.932] ( 7482) Core/Input/Evt: => LOCKS 0x0001 (-) [Keyboard Input 173.932] ( 7482) Core/WindowStack: _dfb_windowstack_inputdevice_listener( 0x7f1ffc60, 0x450280 ) (-) [Keyboard Input 173.932] ( 7482) Core/LayerContext: dfb_layer_context_lock( 0x44b6a8 ) (-) [Keyboard Input 173.933] ( 7482) Core/LayerContext: -> locked 1x now (-) [Keyboard Input 173.935] ( 7482) Core/WM: dfb_wm_process_input( 0x450280, 0x7f1ffc60 ) (-) [Keyboard Input 173.936] ( 7482) WM/Default: Processing input event (device 0, type 0x00000001, flags 0x000000f9)... (-) [Keyboard Input 173.936] ( 7482) IDFBEventBuffer: IDirectFBEventBuffer_WindowReact( 0x7f1ffaa0, 0x457bd0 ) <- type 000100 (-) [Keyboard Input 173.937] ( 7482) Direct/Mem: + 92 bytes [idirectfbinputbuffer.c:846 in IDirectFBEventBuffer_WindowReact()] (-) [Keyboard Input 173.937] ( 7482) IDirectFBWindow: IDirectFBWindow_React() (-) [Keyboard Input 173.937] ( 7482) Core/LayerContext: dfb_layer_context_unlock( 0x44b6a8 )
On Mon, Mar 16, 2009 at 2:47 PM, Ed Camacho <ecama...@gmail.com> wrote: > Sven, > > I appreciate your help thus far. I've taken a look in gdkkeys-directfb.c > and it isn't a matter of not understanding that code, we never hit any of > that code (other than the init). > > I've been using the keyboard driver that comes with DFB1.3 into which I > swapped in some code to grab keypresses. I'm then converting the remote > codes and entering the appropriate values into evt.key_code and dispatching > the event. > > The df_input that I've built on my VM for X11 and a keyboard displays > exactly the same data as the df_input that I've built for my target and > using the remote. > > > > > On Sun, Mar 15, 2009 at 5:02 AM, Sven Neumann <s...@gimp.org> wrote: > >> Hi, >> >> On Sat, 2009-03-14 at 08:07 -0700, Ed Camacho wrote: >> >> > How does DFB send events to GDK? Is there one function that is the >> > entry point? >> >> What exactly is it that you don't understand about the code in >> gdkkeys-directfb.c ? I am really willing to answer your questions, but I >> get the strong feeling that you did not even bother to look at that code >> even though I pointed you to this file some days ago already. >> >> >> Sven >> >> >> >
_______________________________________________ directfb-users mailing list directfb-users@directfb.org http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
