Community
Participate
Working Groups
Created attachment 84790 [details] SnippetHideShellInActivate.java I20071204-1547 Run the attached snippet and press the button. A second shell is made visible but not activated. A display filter for SWT.Activate is installed, which closes the second shell and opens a third shell. When you now click into the second shell, it becomes invisible, but it stays the active shell. The snippet writes the active shell and focus control to stdout every 500ms: - initial and after button pressed: Shell {shell} Button {Show} - after click into shell2: Shell {shell2} Text {} => shell2 is active, but that shell is not visible any more => expected: invisible shell2 should not be the active shell. shell3 should be active after the click. - after click into shell3: Shell {shell3} Text {} - after pressing the Esc key, no shell is active any more: null null => expected: parent shell should take over focus
Is this burning you?
> Is this burning you? No, current workaround is good enough (we explicitly force focus on shell3 when we replace hover shells).
Did you try asyncExec()?
> Did you try asyncExec()? Right, I looked at our code again, and found that we indeed use an asyncExec in this scenario (added for bug 212392). Shell#forceActive() alone would not have helped. (In reply to comment #0) > - after pressing the Esc key, no shell is active any more: > null null > => expected: parent shell should take over focus This works as expected in HEAD.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
