Re: [XonX-Users] XFree86 4.4.0 Release Candidate 1 and Ctrl-right-arrow

[Don M. <ma...@ll...>]

I don't have a solution yet, unfortunately.

I have verified, though, that my console log does show

   Could not find keymapping file USA.keymapping.
   Reading keymap from the system.

when I start XFree86, so it looks like it is using the new keymapping 
mechanism.

I also checked with xev, and the correct keycode are being sent.

I also have discovered that my customizations of the function keys 
have been lost as well.

Where to I look to see what the keyboard map actually is, at any given time?
And should I be comparing keycodes named in that map with keycodes 
being sent by the keyboard (as revealed by xev)?

Thanks
-Don


At 12:35 PM -0800 12/12/03, Torrey Lyons wrote:
>At 8:08 AM -0800 12/12/03, Don MacQueen wrote:
>>I downloaded and installed without difficulty last night, to my 
>>10.3.1 machine at home.
>>
>>I was especially happy to see that hiding (#8 on the feature 
>>differences list) works with other window managers than Apple's, as 
>>I use Afterstep. This alone is enough to keep me using XFree86 
>>rather than Apple's X11.
>
>Cool. Yes, Apple has not really made working with other window 
>managers a priority.
>
>>There was one difference, however.
>>
>>Afterstep supports virtual desktops. It has been possible to move 
>>between desktops using control-right-arrow, control-left-arrow, 
>>ctrl-up-arrow, ctrl-down-arrow. This did not work with the new 
>>candidate. Instead  I got just an echo of the keycode in a shell 
>>window, if one was active. Sorry, I did not keep an example, and 
>>I'm not at that machine right now.
>>
>>Having dealt only minimally with keyboard maps, I'm unsure where to 
>>look for either the cause of the change, or a configuration file to 
>>change to restore the old behavior, or what...
>
>The first thing to do is to make sure that your keyboard map is what 
>it should be. XFree86 uses a different mechanism to build the 
>keyboard map on Panther, so it could be generating a slightly 
>different map. (It should be identical to X11.app's map, however, so 
>one would expect you see the same behavior there as well.) To make 
>sure XFree86 is using the new keymapping mechanisms, check to see 
>that you have lines like the following in your Console log when you 
>start it:
>
>Could not find keymapping file USA.keymapping.
>Reading keymap from the system.
>
>If you instead see:
>
>Using keymapping provided in /System/Library/Keyboards/USA.keymapping.
>
>You should try deleting your USA.keymapping from the XDarwin 
>keyboard preferences. (Just leave it blank.) Then restart and see if 
>it works better.
>
>In any case, you can see what the Control and arrow keys give you by 
>running xev from an xterm window. Put the cursor in the xev window 
>and then type one at a time Control, Left-Arrow, Up-Arrow, etc. You 
>should see something like:
>
>KeyPress event, serial 24, synthetic NO, window 0xe00001,
>     root 0x57, subw 0x0, time 1813482108, (104,76), root:(464,218),
>     state 0x0, keycode 67 (keysym 0xffe3, Control_L), same_screen YES,
>     XLookupString gives 0 bytes:
>     XmbLookupString gives 0 bytes:
>     XFilterEvent returns: False
>
>KeyRelease event, serial 24, synthetic NO, window 0xe00001,
>     root 0x57, subw 0x0, time 1813482196, (104,76), root:(464,218),
>     state 0x4, keycode 67 (keysym 0xffe3, Control_L), same_screen YES,
>     XLookupString gives 0 bytes:
>
>KeyPress event, serial 24, synthetic NO, window 0xe00001,
>     root 0x57, subw 0x0, time 1813476180, (104,76), root:(464,218),
>     state 0x0, keycode 131 (keysym 0xff51, Left), same_screen YES,
>     XKeysymToKeycode returns keycode: 78
>     XLookupString gives 0 bytes:
>     XmbLookupString gives 0 bytes:
>     XFilterEvent returns: False
>
>KeyRelease event, serial 24, synthetic NO, window 0xe00001,
>     root 0x57, subw 0x0, time 1813476332, (104,76), root:(464,218),
>     state 0x0, keycode 131 (keysym 0xff51, Left), same_screen YES,
>     XKeysymToKeycode returns keycode: 78
>     XLookupString gives 0 bytes:
>
>If one of them does not give what you expect, remember the keycode # 
>you get so that you can fix it with xmodmap later. Then you can do 
>something like:
>
>xmodmap -e "keycode 131 = Left"
>
>If I saw that keycode 131 was broken. (In the case above it is correct.)
>
>I would be interested to know what the solution is to this issue for 
>you to make sure there is not a deeper problem lurking here.
>
>--Torrey
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: SF.net Giveback Program.
>Does SourceForge.net help you be more productive?  Does it
>help you create better code?  SHARE THE LOVE, and help us help
>YOU!  Click Here: http://sourceforge.net/donate/
>_______________________________________________
>XonX-Users mailing list
>Xon...@li...
>https://lists.sourceforge.net/lists/listinfo/xonx-users


-- 
--------------------------------------
Don MacQueen
Environmental Protection Department
Lawrence Livermore National Laboratory
Livermore, CA, USA
--------------------------------------