This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 430109 - Un-maximizing the shared area in one perspective also unmaximizes the area in other perspectives
Summary: Un-maximizing the shared area in one perspective also unmaximizes the area in...
Status: VERIFIED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.4   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 4.4 M7   Edit
Assignee: Eric Moffatt CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-11 10:20 EDT by Eric Moffatt CLA
Modified: 2014-04-29 11:12 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 Eric Moffatt CLA 2014-03-11 10:20:41 EDT 
This was likely introduced fairly recently due to some min max work for detached windows...

Start with two perspectives open, max the editor area in both
switch to the other perspective and un-max the EA (trim restores...)

switch back to the first perspective; it's CTF button state indicates it's not maximized but all the trim is still there and working. You can just hit the 'max' button again to put things right...
Comment 1 Eric Moffatt CLA 2014-03-12 11:24:25 EDT 
Committed:

http://git.eclipse.org/c/platform/eclipse.platform.ui.git/commit/?id=b97659ac5a6ae3424e14d5a5a5699ea6f2141677

This was introduced by the fix for bug 377085. The 'findElements' code in MinMaxAddon#restore was searching the whole window rather than just the PRESENTATION (i.e. the stuff the user can see). This ended up finding the maximized placeholder in the other perspective(s).
Comment 2 Eric Moffatt CLA 2014-04-29 11:12:33 EDT 
Verified in 4.4.0.I20140428-2000.