New commits:
http://git.directfb.org/?p=programs/XDirectFB.git;a=commit;h=4995314bcaea4c172a4af5512d180698dfd0259a
commit 4995314bcaea4c172a4af5512d180698dfd0259a
Author: Ville Syrjala <[EMAIL PROTECTED]>
Date: Fri Aug 24 10:16:16 2007 +0300
Use the "evdev" model for XKB.
Switch the XKB model from "pc102" to "evdev". This fixes the key map in
XKB mode. Also use the __XKBDEFRULES__ define instead of the hardcoded
"xfree86".
Note that XDirectFB must be started with the -enableXkb option to get the
correct key map in gnome 2.18. With just an xterm (instead of gnome) the
key map is now correct with or without -enableXkb. I don't claim to
understand XKB but it seems that gnome will somehow enable it later and
load an incorrect key map, unless it was already enabled. All testing was
done w/ xorg-server-1.2.0.
programs/Xserver/hw/directfb/directfbX.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
http://git.directfb.org/?p=programs/XDirectFB.git;a=commit;h=0f6432ad9b07da2339547c3ea22d6d23143ef553
commit 0f6432ad9b07da2339547c3ea22d6d23143ef553
Author: Ville Syrjala <[EMAIL PROTECTED]>
Date: Fri Aug 24 09:57:54 2007 +0300
Fix the XKB sefault.
Initialize the min/max keycodes to the min/max of the X protocol instead
of the actually supported min/max values. For some reason this fixes the
sli->maps segfault in the XKB code :)
programs/Xserver/hw/directfb/directfbKeyboard.c | 16 +++++++++-------
1 files changed, 9 insertions(+), 7 deletions(-)
_______________________________________________
directfb-cvs mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-cvs
