Page MenuHome

Expose fails to bring Blender window to foreground
Closed, ArchivedPublic

Description

This is an issue that Blender has had since the Blender 2.5 port began.

Steps to reproduce:
1. Open Blender
2. Activate Expose, either with a keyboard shortcut or via a mouse gesture
3. Switch away from Blender (to Chrome, Safari, Finder etc)
4. Activate Expose again
5. Try to switch to Blender. Blender (the app) will focus, but the window will not be pulled into the foreground

Alternate steps:
1. Open Blender.
2. Alt-tab to another window (Chrome, Safari, Finder etc)
3. Activate Expose and click on the Blender window. Again, Blender (the app) will focus, but the window will not.

On the second attempt (as in, after the first focus has failed) the Blender window WILL be pulled into the foreground 100% of the time.
On that note, alt-tabbing WILL ALWAYS focus Blender properly. Only Expose seems to have this issue.

Event Timeline

Can't redo issue here, Macbook Pro with OS X 10.7.3, using Blender 2.62. Some details about which Blender and OS X versions you are using might help us to redo this.

Also, alt+tab, is that the right shortcut? It does not thing here, cmd+tab works ok though.

Ah, sorry. I assumed the issue was still present in Lion.

I am running Snow Leopard 10.6.8.

This issue has been present in Leopard as well as Snow Leopard.

Nope, issue still present in Lion. (Just upgraded today, finally.)
For example:

1. Open Blender.app
2. Open/switch to Finder.app, and make sure at least one window is open.
3. Open/switch to Safari.app, and make sure at least one window is open.
4. Command-Tab to Finder.app.
5. Using Mission Control, either from a keyboard shortcut, a mouse-stroke shortcut, or the icon on the dock, click on the Blender.app window.
6. Watch as Blender.app comes into the foreground, while the Blender.app window does not.

Ah, I managed to redo it now with those steps. It seems you need to cmd+tab to the other window, and then use expose to go to Blender. Using expose twice to switch does not have the issue.

While I don't have access to my Mac at the moment, you could also try this out with switching apps using other methods? Perhaps opening an app, and then expose to Blender.app.... Or perhaps just clicking on an App in the Dock, instead of just cmd-tabbing.

Brecht, you told you've managed to reproduce, might you please look if it's blender failure or something more specific? Thanks!

Can't reproduce it on Mac OS 10.8 and Blender 2.64 testbuild 2.

Assuming this is fixed as Renan could not reproduce it anymore.

Can be reopened if the issue is re-confirmed by Clayton or Brecht.

Thomas Dinges (dingto) changed the task status from Unknown Status to Archived.Sep 29 2012, 10:33 PM