Community
Participate
Working Groups
This happens in all perspectives I tried except Java Perspective. For instance in * Debug * CVS Repo Exploring * Synchronize Steps to reproduce 1. open a file in an editor with no other open editors 2. maximize editor 3. close editor Result: all views in the perspective remain minimized Expected Result: view get shown again -- Configuration Details -- Product: Eclipse SDK 4.2.2.v201302041200 (org.eclipse.sdk.ide) Installed Features: org.eclipse.platform 4.2.1.v20130118-173121-9MF7GHYdG0B5kx4E_SkfZV-1mNjVATf67ZAb7
I believe this bug is directly related to bug 394395 @Committers - Mark as duplicate?
This still happens in Eclipse 4.3
Works fine in 4.4 and 4.3.1. What build are you still seeing this in? *** This bug has been marked as a duplicate of bug 394395 ***
This is not a duplicate. I am attaching a few screenshots to document this.
Created attachment 234760 [details] Step 1 (Java Perspective)
Created attachment 234761 [details] Step 2 (Java Perpective)
Created attachment 234762 [details] Step 3 (Java Perspective)
Created attachment 234763 [details] Step 1 (Debug Perspective)
Created attachment 234764 [details] Step 2 (Debug Perspective)
Created attachment 234765 [details] Step 3 (Debug Perspective)
This screenshots were just taken from Eclipse 4.4M1. As you can see the workbench behaves differently after closing the maximized editor in Java and Debug perspectives.
(In reply to comment #11) > This screenshots were just taken from Eclipse 4.4M1. > As you can see the workbench behaves differently after closing the maximized > editor in Java and Debug perspectives. Can be reproduced using 4.4 M1 and new workspace.
I've located the issue and I'll fix it tomorrow. The problem is in the unzoomSharedArea() in WorkbenchPage where it searches the 'window' for the shared area placeholder rather than the current perspective. Each perspective has its own placeholder (and its own max/min state).
Btw the test is that it's not tied to any particular perspective, just the first one in the stack.
COmmitted: http://git.eclipse.org/c/platform/eclipse.platform.ui.git/commit/?id=e87eb3fa52294db594ad8aa3bbfd0e91ae480f0a The unzoomSharedArea() method now correctly locates the correct placeholder. NOTE: I really think that this constitutes bad UI behavior. The *User* has maximized the EA and I don't think it's appropriate that the IDE arbitrarily decides that they were wrong. Why do you folks think that this is good ? You can still access your views...
Verified in 4.4.0.I20130915-2000. Verified as 'fixed'. The first (external) defect that comes in saying that this is bad will also likely get 'fixed'...