Thread: [XonX-Users] XFree86 4.4.0 Release Candidate 1 and Ctrl-right-arrow
Brought to you by:
torrey
From: Don M. <ma...@ll...> - 2003-12-12 16:08:43
|
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. 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... Thanks -Don At 3:14 PM -0800 12/10/03, Torrey T. Lyons wrote: >We have a candidate! The first release candidate for XFree86 4.4.0 >is now available. The upcoming 4.4.0 release is expected to be the >basis for future releases of Apple's X11. This release candidate has >no known bugs on Mac OS X, but it needs testing so bug reports are >greatly appreciated. XFree86 4.4.0 provides identical performance to >Apple's X11 on Panther and is fully compatible with quartz-wm. In >addition this release fixes several bugs present in Apple's X11. > >Prebuilt binaries for Jaguar and Panther can be downloaded from ><ftp://ftp.xfree86.org/pub/XFree86/snapshots/4.3.99.901/binaries/>. >Both Panther and Jaguar use the binaries in the Darwin-ppc-7.x >directory. Download all *.tgz files, Xinstall.sh, and extract. Then >run "sudo sh Xinstall.sh" from the directory you downloaded to. This >will install everything for you. Please report any bugs to >de...@xf.... (Note if you build XFree86 for yourself that this >release was built from source newer then the xf-4_3_99_901 tag.) > >Following is a summary of the most significant differences between >Apple's X11 1.0 and XFree86 4.4.0: > >BUG FIXES: > >1. Threaded direct GLX works correctly. > >2. The X11 GL library does not export all the GLU symbols. > >3. All scripts and man pages do not begin with "#pragma" line. This >bug causes various problems including scripts not working for users >with tcsh as their shell and manpage formatting being broken. > >4. The Freetype library is fully backwards compatible with earlier >versions. (This was a bug in XFree86 4.3.0, which Apple's X11 >inherited.) > >FEATURE DIFFERENCES: >(Some of the feature differences represent new features in XFree86 >4.4.0, while some are features of Apple's X11 that have not yet been >incorporated in XFree86.) > >1. XFree86 supports IPv6. > >2. There is no "pseudo-fullscreen" mode. XFree86's fullscreen mode >has a real root window which works with xmag and twm, but you can't >dynamically switch between fullscreen and rootless modes. > >3. XFree86 does not track Aqua keyboard layout changes while it is >running. XFree86 reads the Aqua keyboard layout at startup time. >While running, the X11 keymap should be changed with xmodmap. > >4. XFree86 is supported back to Mac OS X 10.1. > >5. XFree86 only interprets Command key shortcuts if the cursor is in >the menubar. > >6. XFree86 does not support changing the screen layout or color >depth while it is running. > >7. XFree86 has no "Applications" menu for launching frequently used >X11 clients. > >8. Hiding the XFree86 application works when using any window >manager. (Apple's X11 only supports hiding with quartz-wm.) > >9. XFree86 supports cut-and-paste between Aqua and X11 windows when >quartz-wm is not running. If quartz-wm is running, XFree86 will let >quartz-wm handle cut-and-paste as it generally does a better job. > >10. XFree86 allows arbitrary modifier keys to be used in emulating a >multi-button mouse. These can be specified from the Preferences UI. > >--Torrey >_______________________________________________ >x11-users mailing list | x11...@li... >Help/Unsubscribe/Archives: >http://www.lists.apple.com/mailman/listinfo/x11-users >X11 for Mac OS X FAQ: http://developer.apple.com/qa/qa2001/qa1232.html >Report issues, request features, feedback: >http://developer.apple.com/bugreporter >Do not post admin requests to the list. They will be ignored. -- -------------------------------------- Don MacQueen Environmental Protection Department Lawrence Livermore National Laboratory Livermore, CA, USA -------------------------------------- |
From: Torrey L. <to...@mr...> - 2003-12-12 20:37:25
|
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 |
From: Don M. <ma...@ll...> - 2003-12-17 15:27:07
|
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 -------------------------------------- |
From: Torrey L. <to...@mr...> - 2003-12-17 23:07:16
|
At 7:26 AM -0800 12/17/03, Don MacQueen wrote: >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. Cool. >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. What do you mean by this? Did you customize your function keys in Afterstep? For me all the F# keys are sent correctly except for F9-F11 which are intercepted by Expose. If you are seeing all the correct keysyms being sent it sounds like you may have erased or moved aside your Afterstep preferences while you were installing XFree86 4.4 RC 1. Are all your configuration files in the right place for Afterstep? You may have also had some tweaking of your keymap in /etc/X11 before? Did you customize anything in /etc/X11 previously that could be overwritten by the update? >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)? With "xmodmap -pk" you can get a list of the complete keymap. By looking at the keysym returned by xev you can see what keysym the X server is sending to the X clients. You can also compare the keycodes in xev to see what keysym will be sent by looking up that keycode in the output from "xmodmap -pk". You might also want to check "xmodmap -pm" and make sure that Control_L (left control key) really is the key which gives the control modifier. It should look something like: [65:~] torrey% xmodmap -pm xmodmap: up to 2 keys per modifier, (keycodes in parentheses): shift Shift_L (0x40), Shift_R (0x44) lock Caps_Lock (0x41) control Control_L (0x43), Control_R (0x46) mod1 Mode_switch (0x42), Mode_switch (0x45) mod2 Meta_L (0x3f) mod3 mod4 mod5 How the X clients choose to interpret the keysyms sent by the X server is up to them. If Afterstep is seeing the keysyms you think it should but not doing what you want, then the problem is probably not with the keymap. --Torrey >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 >-------------------------------------- > > >------------------------------------------------------- >This SF.net email is sponsored by: IBM Linux Tutorials. >Become an expert in LINUX or just sharpen your skills. Sign up for IBM's >Free Linux Tutorials. Learn everything from the bash shell to sys admin. >Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click >_______________________________________________ >XonX-Users mailing list >Xon...@li... >https://lists.sourceforge.net/lists/listinfo/xonx-users |