Community
Participate
Working Groups
My issue is the following : At some point, a user is connecting to a database, so perspective is switched to user mode. If the debugger is then to be started and attached to this session, a new workbench window is opened, and switched in debug perspective. But if the first window had the debug perspective opened, generating a debug event will trigger the debug view in both windows, switching the first one from the user perspective to the debug perspective, which is not really fair. So I tried to close all the perspectives of the first window, execpt the user one, to ensure that it was likely that the debug view was not opened in the first window. But there is no way to enumerate the opened perspectives for the window page.... So I did just : pg = win.getActivePage(); pg.close(); wb.showPerspective( id, win ); But this resets the perspective (always triggers my IPerspectiveFactory.createInitialLayout()), whereas the user persp. it is generally present and may have been changed a bit... Thanks for any info, but I felt that not being able to do that is kind of bug... --Steve
In fact the issue is more complex than that. I could do witout the debug perspective closing, provided I manage to have the debug PerspectiveManager work for me, i.e. not messing with getActiveWorkbenchWindow() (seems to fail even when changing the persp to switch) Decreased bug priority, logging another one. --Steve
Generally we don't recommend programmatically closing perspectives. This can be disorienting to the user. I'll have to think about this one...
I understand it is not fair to close perspectives. I worked around the bug of the DebugUI/PerspectiveManager (#44914), so this one does not annoy me anymore. (But I feel that products based on eclipse may want to strip down completely the UI, and hide the notion of perspective, which is ok for a developper but not for an end-user) You can decrease priority/severity at you will or even make it an enhancement request. Bye --Steve
*** Bug 78465 has been marked as a duplicate of this bug. ***
Reassigning bugs in component areas that are changing ownership.
Is this still a problem in 3.3? PW
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. -- The automated Eclipse Genie.
This bug is marked as stale for some time. If it is still relevant for the current release, please reopen and remove the stalebug whiteboard tag.
