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

Bug 171879

Summary: [Trim] Moving minimized view weirdness in 3.3 presentation
Product: [Eclipse Project] Platform Reporter: Andrew Niefer <aniefer>
Component: UIAssignee: Eric Moffatt <emoffatt>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: P3    
Version: 3.3   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments:
Description Flags
screenshot none

Description Andrew Niefer CLA 2007-01-26 17:47:17 EST 
Using 3.3 presentation in I20070123-1715

1. Minimize (for example) the search view
2. Go to the trim stack and click the button for that view to bring it up.
3. Drag the tab to move the view to a new position
4. Minimize the view from the new position

Result: It creates a new trim stack for the new position.  The old trim stack still contains the view.  We can restore both and now have 2 search views.

Click the [x] to close the new view, the original view goes away, the new one stays.  Click the [x] again, the [x] goes away, the view frame stays.
View stacks are now in a wierd state.  
see screenshot.
Comment 1 Andrew Niefer CLA 2007-01-26 17:47:43 EST 
Created attachment 57633 [details]
screenshot
Comment 2 Eric Moffatt CLA 2007-01-29 14:42:23 EST 
This is a known issue with the current implementation. There are a number of operations that can cause the TrimStack/Presentation to get out of synch that become available through the use of operations on the FastViewPane (close is another problem).

We're already updating the TrimStack / FVB story so that both view dragging and close are handled through the use of a common FastViewManager so that whatever we do is shared between the legacy FVB handling and the new TrimStacks.
Comment 3 Eric Moffatt CLA 2007-01-29 14:44:33 EST 
Aha, I found the other one...


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