Bug 37042 - can't close when minimized
Summary: can't close when minimized
Status: VERIFIED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Debbie Wilson CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-04-29 06:21 EDT by Tom Hofmann CLA
Modified: 2004-02-11 11:56 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tom Hofmann CLA 2003-04-29 06:21:22 EDT
1. eclipse with a dirty editor
2. minimize eclipse to the Windows taskbar, 
3. right-click on eclipse' task in the taskbar and select "Close"
4. eclipse does not restore and appears to hang due to the "save resources" 
dialog which does not show up
5. if you hit <enter> or <esc> eclipse behaves as normal - without display 
however

--> eclipse should restore its position when the user closes the application 
from the taskbar, so it can show messages and dialogs.
Comment 1 Debbie Wilson CLA 2003-04-29 15:37:55 EDT
Tom, I'm having trouble reproducing this.  I'm using integration build 
I20030422.  I've tried it with a flat text file (no extra processing such as a 
build required when you save this file) and on a java file (build triggered on 
the save).  In both cases, when I went to the task bar and selected 'close' on 
the Eclipse task, the 'save resources' dialog did show up.  Are you using the 
stable 2.1 release or a subsequent build?  Is there anything in the .log file?
Comment 2 Tom Hofmann CLA 2003-04-30 04:01:17 EDT
- its build 200304221030 (haven't checked with the newest integration build yet)
- nothing in the log

I assume the "save resources" dialog does "show up" (it does if eclipse is not 
minimized, and it does react to user input even if not), but since it is modal 
relative to the main window, which is minimized, nothing is shown.

I am using a Matrox Millenium G450 Dual Head graphics adapter with two monitors 
attached, and the driver does some special maximize and window placement stuff, 
which might be an issue. However on a quick test with just one monitor, it 
showed the same behaviour.
Comment 3 Debbie Wilson CLA 2003-05-12 15:51:42 EDT
Tom, can you run Eclipse in a self-hosting mode?
If so, could you try:
- run your target eclipse under debug
- set a breakpoint in org.eclipse.jface.Dialog.getInitialBounds()
- step through the getInitialSize() and getInitialLocation() methods
- see if there are any unexpected values (e.g. 0 or -1 for size, or 
coordinates that exceed the display bounds)
Comment 4 Tom Hofmann CLA 2003-05-13 05:22:18 EDT
Debbie,
I have stepped thru Window.initializeBounds() (I assume that's what you 
meant?), but all values were correct and the same as if the eclipse is not 
minimized.

But: I just checked and found out that all other Windows applications show the 
same behaviour (including Notepad and MS Word), so I guess it's either Win 2000 
or dual head related, or both.

Propose to resolve as OS bug.

Comment 5 Debbie Wilson CLA 2003-05-14 12:18:17 EDT
Resolving as per your suggestion.  Thanks.

Comment 6 Debbie Wilson CLA 2004-02-11 11:56:45 EST
Marking as verified.  This appears to be a bug not related to Eclipse.