I've once again rolled a new beta release of XQuartz. 2.5.0_beta2 includes multiple bug fixes for issues recently marked as "fixed" in trac. Please check out the full ChangeLog for details. http://xquartz.macosforge.org/trac/wiki/ChangeLog There are two points that I'd like to highlight: 1) We're now using mesa's gl.h rather than the one we were using before (which indirectly included OpenGL.framework's gl.h). This avoids issues where the prototypes between the two versions differ. 2) The "stuck pointer" issue should now be fixed. If you get a pointer stuck in the upper left corner after this release, please let me know as I'm under the impression that that issue is now fixed. You can update using XQuartz.app's automatic update feature or manually with this dmg: http://static.macosforge.org/xquartz/downloads/SL/XQuartz-2.5.0_beta2.dmg
On Mon, Feb 1, 2010 at 7:44 PM, Jeremy Huddleston <jeremyhu@apple.com> wrote:
2) The "stuck pointer" issue should now be fixed. If you get a pointer stuck in the upper left corner after this release, please let me know as I'm under the impression that that issue is now fixed.
I can confirm that this mousetrap issue is gone after I installed this new version 2.5.0_beta2. Both previous test case and xmgrace are behaving correctly. Thanks! -- Mengjuei
"JH" == Jeremy Huddleston <jeremyhu@apple.com> writes: JH> I've once again rolled a new beta release of XQuartz. 2.5.0_beta2 JH> includes multiple bug fixes for issues recently marked as "fixed" in JH> trac. Please check out the full ChangeLog for details.
Works fine for me, especially XKB's problem with keyboard shortcuts seems to be fixed. Thanks! -- Marcus
The XKB issue is 50% fixed. I'm glad that your use case is working, but other users should not panic if they're still having some problems. I believe the remaining issue should be restricted to some keys repeating that shouldn't and others that don't repeat that should. This is because the "should we repeat" metadata is being inherited from an incorrect keymap and not getting clobbered correctly anymore. I have what I think can be a workaround for the remaining issues, but I'm not satisfied with it 100% yet. It should be there in rc1 (which I hope to have ready in a few weeks). Thanks for the feedback, Jeremy On Feb 6, 2010, at 00:44, Marcus Crestani wrote:
"JH" == Jeremy Huddleston <jeremyhu@apple.com> writes: JH> I've once again rolled a new beta release of XQuartz. 2.5.0_beta2 JH> includes multiple bug fixes for issues recently marked as "fixed" in JH> trac. Please check out the full ChangeLog for details.
Works fine for me, especially XKB's problem with keyboard shortcuts seems to be fixed.
Thanks!
-- Marcus _______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
Hi You may be aware of the info below, or not: On my macbookpro1,1 running 10.6.2 and 2.5.0_beta2, (and no ~/.* files :-) there seem to be a problem involving CAPS-LOCK and the top (US) keyboard row: In any xterm or xedit or emacs or xev ... Top Row (xev state 0x0): `1234567890-= Top Row + SHIFT (xev state 0x1): ~!@#$%^&*()_+ Top Row + CAPS-LOCK (xev state 0x2): ~!@#$%^78(0-+ Top Row + CAPS-LOCK + SHIFT (xev state 0x3): `1233456&*9)_= looks like only keys 7, 8, 0, and - behave properly. Am I the only one with this odd behavior ? JF Sygnet Jeremy Huddleston wrote:
The XKB issue is 50% fixed. I'm glad that your use case is working, but other users should not panic if they're still having some problems. I believe the remaining issue should be restricted to some keys repeating that shouldn't and others that don't repeat that should. This is because the "should we repeat" metadata is being inherited from an incorrect keymap and not getting clobbered correctly anymore.
I have what I think can be a workaround for the remaining issues, but I'm not satisfied with it 100% yet. It should be there in rc1 (which I hope to have ready in a few weeks).
Thanks for the feedback, Jeremy
On Feb 6, 2010, at 00:44, Marcus Crestani wrote:
"JH" == Jeremy Huddleston <jeremyhu@apple.com> writes: JH> I've once again rolled a new beta release of XQuartz. 2.5.0_beta2 JH> includes multiple bug fixes for issues recently marked as "fixed" in JH> trac. Please check out the full ChangeLog for details.
Works fine for me, especially XKB's problem with keyboard shortcuts seems to be fixed.
Thanks!
-- Marcus
Hi You are not alone. I get the same results on my machine: Model Name: Mac Pro Model Identifier: MacPro4,1 Processor Name: Quad-Core Intel Xeon Processor Speed: 2.26 GHz Number Of Processors: 2 Total Number Of Cores: 8 L2 Cache (per core): 256 KB L3 Cache (per processor): 8 MB Memory: 6 GB Processor Interconnect Speed: 5.86 GT/s Boot ROM Version: MP41.0081.B07 SMC Version (system): 1.39f5 SMC Version (processor tray): 1.39f5 OS X 10.6.2 Build 10C540 XQuartz 2.5.0_beta2 (xorg-server 1.7.4.901) Louis On Feb 6, 2010, at 3:12 PM, Jean-Francois Sygnet wrote:
Hi
You may be aware of the info below, or not:
On my macbookpro1,1 running 10.6.2 and 2.5.0_beta2, (and no ~/.* files :-) there seem to be a problem involving CAPS-LOCK and the top (US) keyboard row:
In any xterm or xedit or emacs or xev ...
Top Row (xev state 0x0): `1234567890-=
Top Row + SHIFT (xev state 0x1): ~!@#$%^&*()_+
Top Row + CAPS-LOCK (xev state 0x2): ~!@#$%^78(0-+
Top Row + CAPS-LOCK + SHIFT (xev state 0x3): `1233456&*9)_=
looks like only keys 7, 8, 0, and - behave properly.
Am I the only one with this odd behavior ?
JF Sygnet
Jeremy Huddleston wrote:
The XKB issue is 50% fixed. I'm glad that your use case is working, but other users should not panic if they're still having some problems. I believe the remaining issue should be restricted to some keys repeating that shouldn't and others that don't repeat that should. This is because the "should we repeat" metadata is being inherited from an incorrect keymap and not getting clobbered correctly anymore. I have what I think can be a workaround for the remaining issues, but I'm not satisfied with it 100% yet. It should be there in rc1 (which I hope to have ready in a few weeks). Thanks for the feedback, Jeremy On Feb 6, 2010, at 00:44, Marcus Crestani wrote:
"JH" == Jeremy Huddleston <jeremyhu@apple.com> writes: JH> I've once again rolled a new beta release of XQuartz. 2.5.0_beta2 JH> includes multiple bug fixes for issues recently marked as "fixed" in JH> trac. Please check out the full ChangeLog for details.
Works fine for me, especially XKB's problem with keyboard shortcuts seems to be fixed.
Thanks!
-- Marcus
Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
Yes, this is a known issue and related to the meta-data spillover that I mentioned. Basically, some of the number keys are tagged as though they were letters, so they're "shifting" with capslock on. This should be resolved with what I'm working on for rc1. --Jeremy On Feb 6, 2010, at 12:12, Jean-Francois Sygnet wrote:
Hi
You may be aware of the info below, or not:
On my macbookpro1,1 running 10.6.2 and 2.5.0_beta2, (and no ~/.* files :-) there seem to be a problem involving CAPS-LOCK and the top (US) keyboard row:
In any xterm or xedit or emacs or xev ...
Top Row (xev state 0x0): `1234567890-=
Top Row + SHIFT (xev state 0x1): ~!@#$%^&*()_+
Top Row + CAPS-LOCK (xev state 0x2): ~!@#$%^78(0-+
Top Row + CAPS-LOCK + SHIFT (xev state 0x3): `1233456&*9)_=
looks like only keys 7, 8, 0, and - behave properly.
Am I the only one with this odd behavior ?
JF Sygnet
Jeremy Huddleston wrote:
The XKB issue is 50% fixed. I'm glad that your use case is working, but other users should not panic if they're still having some problems. I believe the remaining issue should be restricted to some keys repeating that shouldn't and others that don't repeat that should. This is because the "should we repeat" metadata is being inherited from an incorrect keymap and not getting clobbered correctly anymore. I have what I think can be a workaround for the remaining issues, but I'm not satisfied with it 100% yet. It should be there in rc1 (which I hope to have ready in a few weeks). Thanks for the feedback, Jeremy On Feb 6, 2010, at 00:44, Marcus Crestani wrote:
"JH" == Jeremy Huddleston <jeremyhu@apple.com> writes: JH> I've once again rolled a new beta release of XQuartz. 2.5.0_beta2 JH> includes multiple bug fixes for issues recently marked as "fixed" in JH> trac. Please check out the full ChangeLog for details.
Works fine for me, especially XKB's problem with keyboard shortcuts seems to be fixed.
Thanks!
-- Marcus
Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
participants (5)
-
Jean-Francois Sygnet
-
Jeremy Huddleston
-
Louis Zulli
-
Marcus Crestani
-
Mengjuei Hsieh