Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 352206

Summary: Perspective configuration lost without warning when using multiple windows
Product: [Eclipse Project] Platform Reporter: Tobias Oberlies <t-oberlies>
Component: IDEAssignee: Platform-UI-Inbox <Platform-UI-Inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: daniel_megert
Version: 3.7   
Target Milestone: ---   
Hardware: PC   
OS: Windows Vista   
Whiteboard:

Description Tobias Oberlies CLA 2011-07-15 08:49:54 EDT
When using a single window, closing that window (in Windows) closes Eclipse - but only after showing a confirmation dialog.

When using multiple windows, the behaviour is different: The window is closed without a warning - and all perspective configurations are lost (cf. bug 308350). This can be very annoying, especially if you have many perspective customizations as I usually have.

I would expect a dialog that warns me about the implications of closing one of multiple windows. Something along the lines of "Closing this window closes all perspective in the window. Do you want to continue?"
Comment 1 Paul Webster CLA 2011-07-18 07:18:36 EDT
Additional popups when closing a window is a pretty heavy handed UI metaphor.  On top of that, we would have to provide a preference (ASK_ON_WINDOW_CLOSE maybe) and set it to false because that's the default behaviour.  I feel that would make this mostly a moot point.

*** This bug has been marked as a duplicate of bug 11757 ***
Comment 2 Dani Megert CLA 2011-07-18 11:29:46 EDT
>This can be very annoying, especially if you have many perspective
>customizations as I usually have.

In 3.x you can save your custom perspectives but that's currently not working in 4.1 but will be fixed in 4.1.1, see bug 339130.
Comment 3 Tobias Oberlies CLA 2011-07-22 02:54:49 EDT
(In reply to comment #2)
> In 3.x you can save your custom perspectives but that's currently not working
> in 4.1 but will be fixed in 4.1.1, see bug 339130.

Thanks for pointing me to this possibility. This solves the issue for me :-)