Here's the promised release to fix the spaces interaction bug in 2.3.3.1... http://xquartz.macosforge.org/trac/wiki/X112.3.3.2 http://xquartz.macosforge.org/downloads/X11-2.3.3.2.dmg /wear brown-paper-bag --Jeremy On May 17, 2009, at 16:08, Jeremy Huddleston wrote:

ugg... face/palm ... I'll have a brown-bag fix for that.

On May 17, 2009, at 15:48, Richard Cobbe wrote:

...

I upgraded to MacOS 10.5.7 a while back and to XQuartz 2.3.3.1 today. I'm having some difficulty with the interaction between Spaces and XQuartz. (Forgive me please if this has already been discussed on the list; I did a quick trawl through the archives and open bug reports but couldn't find anything.)

I have Spaces configured with the default 2x2 layout, and with all X11 windows appearing on space #1. Before the upgrade (XQuartz 2.3.2.1, I believe), this behaved in the way that I'd expect: using cmd-tab to switch to X11 switched to space #1 and brought all X windows to the foreground. All new X11 windows (clients and support windows, like the preferences box) appeared on space #1.

Now, things are weird. This is still fairly new and complicated, so I may be missing some details, but here's what I've observed:

- When I start a new X client, it appears on Space #1, as I expect.

- X server support windows (preferences, About X11) appear on space #1, and opening these causes the computer to switch to space #1.

- If I'm looking at another app on Space #3 (say) and activate X11 with cmd-tab, then the computer does *not* change to space #1 but instead moves all existing X client windows to the foreground of the current space. X has input focus. If I have an X support window open, that does *not* move to the new space.

- If I'm running X in Space #3, say, and I open a new X client, it appears on space #1 as above. But the computer does not switch to space #1; it stays on space #3.

Bullet points 1 & 2 are the expected behavior. Bullet point 3 is the big problem; without it, #4 goes away.

Unfortunately, because I didn't upgrade MacOS and Xquartz at the same time, I can't say for sure whether it's the OS or X server upgrade that caused the change in behavior. I *think* it's the X server upgrade. Also, FWIW, after the X server upgrade, I did restart the X server, but I haven't logged out or rebooted the machine (which no longer seem to be required steps in the process).

Is there a workaround? Should I file a bug report?

Thanks,

Richard _______________________________________________ Do not post admin requests to the list. They will be ignored. X11-users mailing list (X11-users@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/x11-users/jeremyhu%40freedesktop.org

This email sent to jeremyhu@freedesktop.org

_______________________________________________ Do not post admin requests to the list. They will be ignored. X11-users mailing list (X11-users@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/x11-users/jeremyhu%40freedesktop.org

This email sent to jeremyhu@freedesktop.org