On Tue, Aug 28, 2007 at 11:05:22AM +0200, Mickael Istria wrote: > I took a deeper look at the error I reported. > > Actually, it seems that < driver_get_keymap_entry >, which computes a > keysym from a basic event, requires to have Virtual Terminals > activated to get 'value' and then compute symbol. (line is 1190 if I > remember...)
Right. It simply reads the kernel keymap and uses that. > I desactivated VT because it won't be used on my system. < > driver_get_keymap_entry > body was not run, in confirmity with the > condition line 1190. > > So VT and linux_input keyboards are not compatible. Adding warning > could be useful. > > > But I keep hope... > I there a "normal" way to make linux_input keyboard work without VT? No. Well it still works but there's no keymap. > If no, is there any good reason to justify it? No one has had the time or interest to implement anything better. > The easiest solution I can see in my situation is to modify < > driver_get_keymap_entry > and < keyboard_get_symbol >, and make it by > myself using only keycodes. That's one option. Probably the easiest option if you're only interested in handling one specific case. > This solution is really ugly. Can you see > something better? Implement a nice generic keymap support in DirectFB. I think ideally it should support per device keymaps, and probably per window keymaps too. Also it might be nice if it could use xkb keymaps (or at least provide a conversion tool of some sort). -- Ville Syrjälä [EMAIL PROTECTED] http://www.sci.fi/~syrjala/ _______________________________________________ directfb-users mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
