Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 179702 - [Trim] [Min/Max] Editor area has wrong state if maximized editor gets closed
Summary: [Trim] [Min/Max] Editor area has wrong state if maximized editor gets closed
Status: VERIFIED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.3 M7   Edit
Assignee: Eric Moffatt CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 183026 (view as bug list)
Depends on:
Blocks: 153957
  Show dependency tree
 
Reported: 2007-03-28 06:14 EDT by Dani Megert CLA
Modified: 2007-05-22 09:18 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dani Megert CLA 2007-03-28 06:14:17 EDT 
3.3 M6

1. open an editor
2. maximize editor
   ==> views are collapsed
   ==> I could bring them back by clicking the 'Restore' icon of the editor area
3. close the editor (while still maximized)
   ==> editor area icon is now 'Maximize' but should be 'Restore'
   ==> to bring back views I need to click twice on the icon
Comment 1 Benjamin Pasero CLA 2007-03-28 07:08:28 EDT 
See also Bug 179387
Comment 2 Eric Moffatt CLA 2007-03-28 13:38:39 EDT 
This seems to be the bug of the day...;-).


*** This bug has been marked as a duplicate of bug 179255 ***
Comment 3 Dani Megert CLA 2007-05-02 03:21:08 EDT 
This is neither a dup nor fixed.
Comment 4 Dani Megert CLA 2007-05-02 03:25:30 EDT 
>This is neither a dup nor fixed.
What I wanted to say is: this is exactly a dup of bug 179255. Instead this bug here was just about the wrong state which got correctly fixed. Bug 179255 however did not get fixed but rather set to WONTFIX.
Comment 5 Dani Megert CLA 2007-05-02 03:49:14 EDT 
Verified using I20070502-0010.
Comment 6 Eric Moffatt CLA 2007-05-22 09:18:33 EDT 
*** Bug 183026 has been marked as a duplicate of this bug. ***