Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 320321 - closing a minimized view leaves empty chunk in the editor
Summary: closing a minimized view leaves empty chunk in the editor
Status: CLOSED DUPLICATE of bug 320243
Alias: None
Product: e4
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 1.0   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-19 16:38 EDT by Susan McCourt CLA
Modified: 2010-07-22 18:34 EDT (History)
1 user (show)

See Also:

Attachments
screenshot (137.13 KB, image/png)
2010-07-19 16:38 EDT, Susan McCourt CLA 		no flags Details
View All 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 Susan McCourt CLA 2010-07-19 16:38:00 EDT 
Created attachment 174672 [details]
screenshot

Win7, Build id: I20100718-2237

This is continuing the scenario described in bug 315807.

1. Open a file.
2. Detach the 'Outline' view.
3. Bring it back to the right of the editor.
4. Minimize the 'Outline' view.

At this point the icon goes to the trim but the view also floats above the
editor as a fast view.  This is bug 315807.

For grins, I then tried to close the outline view with the close box.  The view disappeared and I had an empty chunk (blue background) in the editor where the view used to be.  Resizing doesn't fix the problem.  There is also a restore icon in the trim (or maybe in the ghosted view?)
Comment 1 Susan McCourt CLA 2010-07-19 16:39:29 EDT 
In this state, one can hover over the restore icon and see the button become active.  Pushing it does nothing and there is no NPE in the log.
Comment 2 Remy Suen CLA 2010-07-19 17:07:22 EDT 
I've seen the "block" problem. This is probably a duplicate/manifestation of bug 320243.
Comment 3 Susan McCourt CLA 2010-07-22 18:34:40 EDT 
indeed, the fix for 320243 fixes this problem.

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