Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 339233 - [Min/Max] Discrepancy between 'Maximize' button and Ctrl+M
Summary: [Min/Max] Discrepancy between 'Maximize' button and Ctrl+M
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-08 10:30 EST by Remy Suen CLA
Modified: 2019-11-08 02:11 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Remy Suen CLA 2011-03-08 10:30:53 EST
I20110307-2110

1. Activate the 'Package Explorer'.
2. Ctrl+M
3. Click on the 'Outline' view's icon.
4. Click on its 'Maximize' button.
5. It takes up all the space but the 'Package Explorer' is still behind it.
6. If you restore the 'Outline' view, it will show up on the side again as if it was a fast view.

4. Ctrl+M.
5. Notice that the 'Package Explorer' has now been minimized to the trim.
6. If you restore the 'Outline' view now the whole perspective goes back to its regular unzoomed state.
Comment 1 Remy Suen CLA 2011-03-08 11:14:30 EST
If the view is a fast view then there is no difference between clicking on the 'Maximize' button and Ctrl+M.
Comment 2 Dani Megert CLA 2011-03-16 07:53:47 EDT
Funny!

Before 3.6 the second Ctrl+M behaved the same as clicking 'Maximize'.

I think Ctrl+M and clicking 'Maximize' should behave the same and they should do the same when invoked the second time i.e. in the given example the 'Package Explorer' should be minimized to the trim.
Comment 3 Eclipse Genie CLA 2019-11-08 02:11:14 EST
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.