I've cross compiled DFB 1.3 for my embedded device. I have no keyboard so
I've modified the keyboard driver to read from my remote. Using dfinput, I
can tell that my keystrokes are getting into DFB ok. Here are logs:
(-) [Keyboard Input 9.256] ( 5968) Core/Input/Evt: -> (01) KEYPRESS
(-) [Keyboard Input 9.256] ( 5968) Core/Input/Evt: -> KEYID
0xf643
(-) [Keyboard Input 9.256] ( 5968) Core/Input/Evt: => TIMESTAMP
946693460.041443
(-) [Keyboard Input 9.256] ( 5968) Core/Input/Evt: => KEYCODE -1
(-) [Keyboard Input 9.256] ( 5968) Core/Input/Evt: => KEYID
0xf643
(-) [Keyboard Input 9.256] ( 5968) Core/Input/Evt: => KEYSYMBOL
0xf002
(-) [Keyboard Input 9.256] ( 5968) Core/Input/Evt: => MODIFIERS
0x0000
(-) [Keyboard Input 9.257] ( 5968) Core/Input/Evt: => LOCKS
0x0000
(-) [Keyboard Input 9.257] ( 5968) Core/WindowStack:
_dfb_windowstack_inputdevice_listener( 0x7f7ffc88, 0x44c778 )
(-) [Keyboard Input 9.257] ( 5968) Core/LayerContext:
dfb_layer_context_lock( 0x451260 )
(-) [Keyboard Input 9.257] ( 5968) Core/LayerContext: -> locked 1x now
(-) [Keyboard Input 9.257] ( 5968) Core/WM:
dfb_wm_process_input( 0x44c778, 0x7f7ffc88 )
(-) [Keyboard Input 9.257] ( 5968) WM/Default: Processing input
event (device 0, type 0x00000001, flags 0x000000f9)...
(-) [Keyboard Input 9.257] ( 5968) Core/LayerContext:
dfb_layer_context_unlock( 0x451260 )
When I compile some sample GTK test apps (the ones packaged with GTK 2.12.12
for example), I don't see my keystrokes being recognized. As I have no
mouse or keyboard, is it an issue of focus or am I missing something which
"bubbles" the DFB events up to GTK? Do I need to write something which
takes the events and sends them to GTK?
Thanks,
Ed
--
View this message in context:
http://www.nabble.com/DirectFB-keystrokes-in-GTK-tp22445647p22445647.html
Sent from the DirectFB Users mailing list archive at Nabble.com.
_______________________________________________
directfb-users mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
