Bug 76471 - [Presentations] closing minimized view sometimes restores it
Summary: [Presentations] closing minimized view sometimes restores it
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P5 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 153189 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-10-18 11:23 EDT by Rafael Chaves CLA
Modified: 2019-09-06 16:07 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 Rafael Chaves CLA 2004-10-18 11:23:29 EDT 
i20041013

Closing a view in the minimized state sometimes just restore it. This does not
happen for every view, or every time for the same view. Starting with a fresh
workspace, I could notice it happening with the Welcome and Outline views, but
not with the Navigator.

Maybe this expected bahavior, but I could not understand how it could be useful.
Comment 1 Nick Edgar CLA 2004-10-20 12:30:54 EDT 
It appears to depend on whether the minimized state changes the horizontal
position of the close box.  Even when it does work, there is some flash as the
view is unzoomed before closing.

This is probably an interaction between the mouse click causing unzoom, and how
CTabFolder handles mouse up on the buttons.
It would probably be fixed by ensuring that clicking in the close box never unzooms.
Comment 2 Paul Webster CLA 2006-08-09 07:38:21 EDT 
*** Bug 153189 has been marked as a duplicate of this bug. ***
Comment 3 Paul Webster CLA 2006-09-28 15:14:11 EDT 
Is this still a problem in 3.3?

PW
Comment 4 Denis Roy CLA 2007-06-22 09:32:43 EDT 
Changes requested on bug 193523
Comment 5 Eclipse Webmaster CLA 2019-09-06 16:07:18 EDT 
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.