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

Bug 178893

Summary:	[Trim] Closing last maximized editor leaves IDE is an inconsistent state
Product:	[Eclipse Project] Platform	Reporter:	Ed Merks <Ed.Merks>
Component:	UI	Assignee:	Eric Moffatt <emoffatt>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	P3	CC:	marcelop
Version:	3.3
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Ed Merks

2007-03-22 16:49:45 EDT

I picked up I20070321-1800 and was surprised to see the maximize editor behavior had changed.  I'm not sure I like it, but probably there's an option somewhere.  In any case, the new feature is a little buggy.  If you close the last maximized editor, the empty frame that's left over has an icon to maximize it even though it's already maximized.  Hence you need to click the icon twice in order to restore the other views.  It would seem good to fix this before M6...

Comment 1 Ed Merks

2007-03-24 12:03:11 EDT

Another problem I just noticed is that if I have a Java source editor maximized, and I ask to show the type hierarchy for a class, the view opens in a very odd state where it overlays the editor itself.

Comment 2 Eric Moffatt

2007-03-24 23:35:14 EDT

Sorry Ed, missed M6...

I already had it (thus the dup). 

The 'odd' behavior' you see with the viw overlaying the editor is in actuality expected. When the editor (or a view) is maximized it moves the other stacks to the trim (the outside boundary) where they act as fast views. The reasoning behind he change is that the old behavior wouldn't let you even use a view when the editor was maximized; you had to restore -everything-. Now you can either use them as fast views or you can restore the stack containing the one view that you need.

Also, the new behavior maximizes the Editor Area so if you have split the area up (i.e. to compare two files) you get to see both.


*** This bug has been marked as a duplicate of bug 177850 ***