Bug 208232 - [Dialogs] Dialogs should restore maximized state and unmaximized size
Summary: [Dialogs] Dialogs should restore maximized state and unmaximized size
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-31 10:47 EDT by Markus Keller CLA
Modified: 2019-09-06 16:14 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Keller CLA 2007-10-31 10:47:32 EDT
I20071031-0010

Dialogs that automatically save/restore their size currently don't store the 'maximized' state.

When closed in maximized state, the stored size is the whole screen. When the dialog is reopened, it is not maximized, but covers the whole screen. The user has to manually resize the dialog to get it smaller again.

The framework should store
- the size of the dialog in the unmaximized state, and
- the maximized bit.
When the dialog is reopened, the size should be restored, and then the maximized bit should be restored as well. When the user unmaximizes the dialog, its size should be the last size the dialog had in unmaximized state.

Implementation hint: Since there's no SWT event when a dialog is (un)maximized, you probably have to add a resize listener to the shell, and save the size in a field whenever the dialog is resized but is not maximized. When the dialog is closed, store the maximized bit and the size from the field.
Comment 1 Pawel Pogorzelski CLA 2009-03-12 06:52:48 EDT
This is quite annoying while using Apply Patch wizard.
Comment 2 Susan McCourt CLA 2009-07-09 17:37:40 EDT
as per 2009 triage guidelines
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:14:06 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.