Re: [Xquartz-dev] xorg-server on Macports (works with Tiger)
Am 23.12.2008 um 23:55 schrieb Jeremy Huddleston:
Really? Unfortunately I don't have my Tiger box here to test cmd-alt- t... How is this implemented? Is it a menu item?
Yes: (xkill, xkill, "\\U2020")
A key is passed to Appkit instead of X11 to handle if it is a key equivalent and you have 'enable OSX Key equivalents' enabled in your preferences.
It is: "enable_key_equivalents" = 1; Does it mean that in full-screen mode X11 has a leak through which key codes can "escape?" I thought that only three (copy, paste, toggle X11/Quartz), maybe also cut, are in effect. -- Greetings Pete People say that if you play Microsoft CD's backwards, you hear satanic things, but that's nothing, because if you play them forwards, they install MS Windows.
On Dec 24, 2008, at 05:27, Peter Dyballa wrote:
Am 23.12.2008 um 23:55 schrieb Jeremy Huddleston:
Really? Unfortunately I don't have my Tiger box here to test cmd- alt- t... How is this implemented? Is it a menu item?
Yes: (xkill, xkill, "\\U2020")
Then you can add that to the Applications menu for the newer server the exact same way.
Does it mean that in full-screen mode X11 has a leak through which key codes can "escape?" I thought that only three (copy, paste, toggle X11/Quartz), maybe also cut, are in effect.
In fullscreen, "we" don't do anything inside X11.app to restrict key equivalents. We simply activate fullscreen mode, and that trigers rules in OSX that determine which key sequences "escape" from Appkit... we just use the same rules to determine if we should pass a key sequence to X11 or AppKit. Look around line 280: http://cgit.freedesktop.org/xorg/xserver/tree/hw/xquartz/X11Application.m?id...
Hi Jeremy, Another (this time minor) thing: With X11 set for full-screen mode but not open, I type xeyes in Terminal. I get the xeyes window in front of the root window, as I expect. I click the yellow traffic light---I'm using quartz-wm---on the xeyes window. Nothing happens, but if I follow with cmd-opt-a I get to my Desktop with the xeyes window minimized to an icon on my dock. I click that icon and I'm taken back to the root window, but no eyes! Need to do cmd-opt-a twice to correct things. I guess this is a minor issue, but I'd expect to see the xeyes window after clicking on that dock icon. Louis
Ok, please file a bug report at http://xquartz.macosforge.org This is not unique to xeyes (xterm does it too) and will probably take some time to debug... On Dec 24, 2008, at 11:07, Zulli, Louis P wrote:
Hi Jeremy,
Another (this time minor) thing:
With X11 set for full-screen mode but not open, I type xeyes in Terminal. I get the xeyes window in front of the root window, as I expect. I click the yellow traffic light---I'm using quartz-wm---on the xeyes window. Nothing happens, but if I follow with cmd-opt-a I get to my Desktop with the xeyes window minimized to an icon on my dock. I click that icon and I'm taken back to the root window, but no eyes! Need to do cmd-opt-a twice to correct things. I guess this is a minor issue, but I'd expect to see the xeyes window after clicking on that dock icon.
Louis _______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
On Dec 24, 2008, at 2:07 PM, Zulli, Louis P wrote:
Hi Jeremy,
Another (this time minor) thing:
With X11 set for full-screen mode but not open, I type xeyes in Terminal. I get the xeyes window in front of the root window, as I expect. I click the yellow traffic light---I'm using quartz-wm---on the xeyes window. Nothing happens, but if I follow with cmd-opt-a I get to my Desktop with the xeyes window minimized to an icon on my dock. I click that icon and I'm taken back to the root window, but no eyes! Need to do cmd-opt-a twice to correct things. I guess this is a minor issue, but I'd expect to see the xeyes window after clicking on that dock icon.
Louis _______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
This error doesnt happen on my Leopard William Davis frstanATbellsouthDOTnet Mac OS X.5.6 Darwin 9.5.0 XQuartz 2.3.2_rc4 (xorg-server 1.4.2-apple28) Mac Mini Intel Duo @ 1.86 GHz Mundus vult decepi, ego non
AFAICT, this is a long-standing issue (or atleast a regression over Tiger due to something outside of X11). Using the exact same X11.app as Tiger 10.4.11 while on Leopard, I see the same behavior. I won't have access to my Tiger box for the next few days, so could someone confirm how the quartz-wm minimize behavior worked on Tiger with fullscreen X11? I messed around with this for a couple hours and have nothing to show of it. Due to the fact that Tiger's X11 behaves the same way (atleast on Leopard), I'm not going to let this hold up 2.3.2. Right now, there are just two issues on the 2.3.2 list. I can't reproduce either, and sumbitters of the bugs aren't responsive: http://xquartz.macosforge.org/trac/report/3 Does anyone have any information on either of those two issues that would be helpful? If not, I'm going to close them as "worksforme" or "fixed" as appropriate. Thanks, Jeremy On Dec 24, 2008, at 11:07, Zulli, Louis P wrote:
Hi Jeremy,
Another (this time minor) thing:
With X11 set for full-screen mode but not open, I type xeyes in Terminal. I get the xeyes window in front of the root window, as I expect. I click the yellow traffic light---I'm using quartz-wm---on the xeyes window. Nothing happens, but if I follow with cmd-opt-a I get to my Desktop with the xeyes window minimized to an icon on my dock. I click that icon and I'm taken back to the root window, but no eyes! Need to do cmd-opt-a twice to correct things. I guess this is a minor issue, but I'd expect to see the xeyes window after clicking on that dock icon.
Louis _______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
On Dec 24, 2008, at 8:27 PM, Jeremy Huddleston wrote:
so could someone confirm how the quartz-wm minimize behavior worked on Tiger with fullscreen X11?
Actually, it's rather queer, at least on my iMac running 10.4.11 with X11 1.1.3 - XFree86 4.4.0. With an xeyes (for example) window open on the root window, I click the yellow button. Nothing happens, but with cmd-opt-a I return to my desktop with the xeyes window minimized to the dock. I click on that dock icon and the root window appears, with a "warped" small xeyes window (imagine genie effect aborted) just above the bottom of the window. The pupils of the eyes are still active by the way. Creepy. Anyway, two successive cmd-opt-a's and the xeyes window is returned to normal on the root. In summary, the Tiger behavior is also not what one would normally expect!
On Dec 24, 2008, at 19:00, Louis Zulli wrote:
On Dec 24, 2008, at 8:27 PM, Jeremy Huddleston wrote:
so could someone confirm how the quartz-wm minimize behavior worked on Tiger with fullscreen X11?
Actually, it's rather queer, at least on my iMac running 10.4.11 with X11 1.1.3 - XFree86 4.4.0.
With an xeyes (for example) window open on the root window, I click the yellow button. Nothing happens, but with cmd-opt-a I return to my desktop with the xeyes window minimized to the dock. I click on that dock icon and the root window appears, with a "warped" small xeyes window (imagine genie effect aborted) just above the bottom of the window. The pupils of the eyes are still active by the way. Creepy. Anyway, two successive cmd-opt-a's and the xeyes window is returned to normal on the root.
In summary, the Tiger behavior is also not what one would normally expect!
Yeah, that's what I was seeing with Tiger's X11 on Leopard... That's essentially the same as with the current X11 except we don't see that "aborted genie effect". Thanks for testing this out for me. Atleast I know this issue is not a regression! --Jeremy
participants (5)
-
Jeremy Huddleston
-
Louis Zulli
-
Peter Dyballa
-
William Davis
-
Zulli, Louis P