I thought the exposé bug had been fixed quite some while ago? Well I am seeing it again. Is it a regression, or what? I am talking about ticket #78 http://trac.macosforge.org/projects/xquartz/ticket/78 which is closed, with resolution: duplicate. Here I must digress and report a bug in the bug tracking system: It doesn't tell you what bug report it is a duplicate of! It should not be possible to close a bug with resolution: duplicate without specifying this vital information, and without that information being visible afterwards. However, I am unable to find it after quite a bit of looking. Anyway, ticket #78 describes exactly what I am seeing, so I won't repeat it here. Xquartz-1.4.0-apple7, X11 2.2.1-rc2 (said to be identical to 2.2.1, so I haven't upgraded), and Ben's quartz-wm. - Harald
That's probably because you're using Ben's quartz-wm which probably doesn't have the fix in it... try with just 2.2.1 and let me know if you can trigger the issue. What exactly was Ben's quartz-wm? --disable-pb-proxy, right? Please file a bug for that at http://bugreport.apple.com, and I'll remember to roll something like that into the next quartz-wm (actually, I want to pull the proxy code out of quartz-wm and into the server completely, but this will atleast give me a reminder about it) --Jeremy On May 3, 2008, at 14:02, Harald Hanche-Olsen wrote:
I thought the exposé bug had been fixed quite some while ago? Well I am seeing it again. Is it a regression, or what?
I am talking about ticket #78
http://trac.macosforge.org/projects/xquartz/ticket/78
which is closed, with resolution: duplicate.
Here I must digress and report a bug in the bug tracking system: It doesn't tell you what bug report it is a duplicate of! It should not be possible to close a bug with resolution: duplicate without specifying this vital information, and without that information being visible afterwards. However, I am unable to find it after quite a bit of looking.
Anyway, ticket #78 describes exactly what I am seeing, so I won't repeat it here. Xquartz-1.4.0-apple7, X11 2.2.1-rc2 (said to be identical to 2.2.1, so I haven't upgraded), and Ben's quartz-wm.
- Harald _______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/xquartz-dev
+ Jeremy Huddleston <jeremyhu@apple.com>:
On May 3, 2008, at 14:02, Harald Hanche-Olsen wrote:
I thought the exposé bug had been fixed quite some while ago? Well I am seeing it again. Is it a regression, or what?
That's probably because you're using Ben's quartz-wm which probably doesn't have the fix in it... try with just 2.2.1 and let me know if you can trigger the issue.
It seems to be there, independently of what quartz-wm I run. I also tried going back to the 2.2.1 Xquartz (1.3.0-apple20) and saw the same thing. So now I am confused - was the bug ever fixed, or not? The only mention of it I can find on trac.macosforge.org is ticket #78, which as I said was closed with resolution: duplicate - and I cannot find said duplicate.
What exactly was Ben's quartz-wm? --disable-pb-proxy, right?
It's called --no-pasteboard. http://lists.macosforge.org/pipermail/xquartz-dev/2008-April/000605.html
Please file a bug for that at http://bugreport.apple.com, and I'll remember to roll something like that into the next quartz-wm (actually, I want to pull the proxy code out of quartz-wm and into the server completely, but this will atleast give me a reminder about it)
You're sure you want it on bugreport.apple.com and not on macosforge.org? I mean, do we even know for sure whether it's a quartz-wm or Xquartz issue? I'll file a bugreport wherever you ask, but want to make doubly sure where. Plus, it would be good to hear if others are seeing it to, or if it's just me. In which case I should first try to figure out what about my setup is triggering it. Anybody? To repeat the bug, put two X windows on top of each other, window A partially or completely obscuring window B. Use exposé to get window B on top, and click on it, in a place which is also on top of window A. Now window A pops back to the top and gets focus. - Harald
Harald, I tried your recipe and could not get it to occur for me. In all cases, the exposé selected window comes to the top with focus. Clicking on the overlap area didn't do anything (as I would expect). I'm running X11 2.2.1 as released. wm_ffm=0, wm_click_through=1, wm_focus_on_new_window=1, wm_limit_size=1 Merle On May 4, 2008, at 3:15 AM, Harald Hanche-Olsen wrote:
Plus, it would be good to hear if others are seeing it to, or if it's just me. In which case I should first try to figure out what about my setup is triggering it. Anybody?
To repeat the bug, put two X windows on top of each other, window A partially or completely obscuring window B. Use exposé to get window B on top, and click on it, in a place which is also on top of window A. Now window A pops back to the top and gets focus.
- Harald
participants (3)
-
Harald Hanche-Olsen
-
Jeremy Huddleston
-
Merle Reinhart