No, this is pretty much what I'm talking about. XKB has a bug whereby it doesn't reset flags on keys when the keymap changes, so we've got our correct keymap, but different keys are being tagged incorrectly because they inherrited those tags from the the default keymap that we clobbered. This is something on the list of "must fix" before 2.5.0 ships. --Jeremy On Dec 17, 2009, at 02:36, Marcus Crestani wrote:
"JH" == Jeremy Huddleston <jeremyhu@apple.com> writes: JH> Please let me know if there are any issues.
I finally got around testing the new beta release. It works fine for me except some keyboard issues...
JH> As of now, there are no known regressions from 1.5 to 1.6 to 1.7 JH> (although there are a few "new" issues common to all of them JH> pertaining to keyboard mapping), [...]
... you probably talked about.
Key combinations I use all the time (e.g. for switching windows) like Command+Arrows, Command+Alt+Arrows, or Command+Shift+Arrows and the like do not work as expected, instead I see stuff like "[c[d0d0c[C[C" inserted in a XTerm, for example. Does this fit in your "new issues" or do you need more information?
Thanks for your great work!
-- Marcus _______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev