Community
Participate
Working Groups
I20040405 1. Have two views (say outline and package explorer) together in the UI in a tab folder. 2. Detach one of the views. 3. Give focus back to the old view and shade it. Notice that the detached view now gets focus. 4. Click anywhere in the eclipse window, the shaded view becomes unshaded.
Cannot reproduce on 20041005 under WinXP. Is this still occurring?
Yes, it still happens here. Focus order is important. To be clearer on the steps: 1. Detach the navigator view 2. Click the Navigator tab (make sure it has focus) 3. Click the tab for the Outline view (last view to have focus was the Navigator) 4. Shade the Outline view => focus now goes to the Navigator view 5. Click in the editor, Outline view becomes unshaded
Also see bug 75714 for a similar sort of problem.
This does not happen on Windows XP. It does happen on Linux GTK+. If you need help reproducing the problem, please see Billy or me. Or, even better, get yourself a GTK+ box.
Hmm... this might happen if GTK was automatically assigning focus to a control in the minimized view when the Shell got focus. Is this possible?
*** Bug 72896 has been marked as a duplicate of this bug. ***
This happens on my XP box but NOT on Paul's Linux box now...curiouser and curioser. I'm passing the buck to Paul for a deeper look because the restoring of the minimized view is part of the workbench activation handling (it's trying to show the activation status on the (minimized) part's tab (which causes it to be restored). *** This bug has been marked as a duplicate of 111658 ***
*** Bug 111658 has been marked as a duplicate of this bug. ***
More Ooops...I didn't need to open 111658.
Over to you Paul...
Is this still a problem in 3.3? PW
I can't repro this on my home box...(XP /w SP2) using the steps outlined (and the default presenation).
Changes requested on bug 193523
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.