Hi, I'm noticing an issue with expose with 2.4.0_rc2 (1.5.3-apple14). I've got a large X11 app (ds9 in this case), with an xterm behind it. I use expose to bring the xterm in front of ds9, but when I click on the xterm it dissappears behind ds9 (and the xterm doesn't become the active window as it should when selecting it with expose). Oddly another xterm open doesn't act in this way. Jamie
+ Jamie Kennea <jamie@pompey.org>:
I'm noticing an issue with expose with 2.4.0_rc2 (1.5.3-apple14). I've got a large X11 app (ds9 in this case), with an xterm behind it. I use expose to bring the xterm in front of ds9, but when I click on the xterm it dissappears behind ds9 (and the xterm doesn't become the active window as it should when selecting it with expose).
Hmm. Is it this bug (fixed 16 months ago) that has come back? http://xquartz.macosforge.org/trac/ticket/2 - Harald
On Aug 12, 2009, at 9:25 AM, Harald Hanche-Olsen wrote:
Hmm. Is it this bug (fixed 16 months ago) that has come back?
It certainly seems the same, but its just affecting this one xterm window (I have 2 others now that work fine), and I can't see what's special about it. xwininfo doesn't reveal anything obvious. Perhaps this is just a weird one-off. Jamie
On Aug 12, 2009, at 07:13, Jamie Kennea wrote:
On Aug 12, 2009, at 9:25 AM, Harald Hanche-Olsen wrote:
Hmm. Is it this bug (fixed 16 months ago) that has come back?
It certainly seems the same, but its just affecting this one xterm window (I have 2 others now that work fine), and I can't see what's special about it. xwininfo doesn't reveal anything obvious. Perhaps this is just a weird one-off.
It's entirely possible that the "bad" xterm window was started before quartz-wm checked in with the server... thus that xterm window wasn't flagged to pass focus events to quartz-wm for handling. Was the rogue xterm started as 'app_to_run' by chance? It might've just won the race against quartz-wm checking in...
On Aug 12, 2009, at 11:21, Jeremy Huddleston wrote:
On Aug 12, 2009, at 9:25 AM, Harald Hanche-Olsen wrote:
Hmm. Is it this bug (fixed 16 months ago) that has come back?
It certainly seems the same, but its just affecting this one xterm window (I have 2 others now that work fine), and I can't see what's special about it. xwininfo doesn't reveal anything obvious. Perhaps this is just a weird one-off.
It's entirely possible that the "bad" xterm window was started before quartz-wm checked in with the server... thus that xterm window wasn't flagged to pass focus events to quartz-wm for handling.
Was the rogue xterm started as 'app_to_run' by chance? It might've just won the race against quartz-wm checking in...
Actually, that shouldn't happen... I added code to quartz-wm to flag all existing windows when it checks in... but still, this might be an odd corner case that I missed. Is it consistently reproduced, or is this the only time you've seen the problem?
On Aug 12, 2009, at 2:21 PM, Jeremy Huddleston wrote:
It's entirely possible that the "bad" xterm window was started before quartz-wm checked in with the server... thus that xterm window wasn't flagged to pass focus events to quartz-wm for handling.
Was the rogue xterm started as 'app_to_run' by chance? It might've just won the race against quartz-wm checking in...
I think you might have something here (I note your later email BTW, so bear with me). I was able reproduce this problem. I work on a great number of computers, and as shortcuts I have little scripts to start xterms with ssh sessions to various computers on my desktop, that I click to run. I just recreated this problem by starting X11 by clicking on one of these icons, which started an Xterm (ssh I believe is irrelevant here). The important thing I think is that sometimes the xterm appears before quartzwm is fully initialized, so appears briefly with no decoration. An xterm that starts in this way suffers the expose problem. A second time I did this, the xterm seemed to appear "fully formed" and didn't have the issue. I did the same thing each time, the 2nd time probably worked because things tend to load faster the 2nd time you run a program. The fix for me will be to always start X11 by clicking on the X11 icon first, as I use X11 99% of the time. It was only due to the Safari 4.0.3 force reboot that I had restarted X11 in this way. Jamie
On Aug 12, 2009, at 13:24, Jamie Kennea wrote:
The important thing I think is that sometimes the xterm appears before quartzwm is fully initialized, so appears briefly with no decoration. An xterm that starts in this way suffers the expose problem.
A second time I did this, the xterm seemed to appear "fully formed" and didn't have the issue.
Jamie, are you using 2.4.0-rc2?
participants (3)
-
Harald Hanche-Olsen
-
Jamie Kennea
-
Jeremy Huddleston