Community
Participate
Working Groups
If you invoke activate(IWorkbenchPart) on a non-active part, that part's workbench window will be activated even if there is another workbench window that's active. On the other hand, if you invoke the method on that particular workbench window's active part, that window will not be activated and will remain in the background. This inconsistency seems wrong to me.
I'm not sure what the difference is between your 2 paragraphs? Do you mean if you pass in window2/part into window1.page.activate(*) it activates window2, but if you call window2.page.activate(*) on window2/part it doesn't? PW
(In reply to comment #1) > I'm not sure what the difference is between your 2 paragraphs? > > Do you mean if you pass in window2/part into window1.page.activate(*) it > activates window2, That doesn't work anyway, we fail if you don't activate through your own page. PW
(In reply to comment #1) > I'm not sure what the difference is between your 2 paragraphs? The first scenario is where you activate a non-active part of a workbench window that's behind (not the active workbench window). That workbench window will be activated. The second scenario is where you activate the currently active part of a workbench window that's behind (not the active workbench window). That workbench window will then not be activated.
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. If the bug is still relevant, please remove the "stalebug" whiteboard tag.
