Bug 111594 - [Misc] Convert dialogs to use inherited size/location persistence
Summary: [Misc] Convert dialogs to use inherited size/location persistence
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform Team Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-05 08:20 EDT by Michael Valenta CLA
Modified: 2019-09-06 16:17 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Valenta CLA 2005-10-05 08:20:07 EDT
From platform-ui-dev

The JFace Dialog class now supports (in builds >20051004) persisting of a 
dialog's location and/or 
size.  For a detailed history of this topic and explanation of how to get this 
behavior, 
see https://bugs.eclipse.org/bugs/show_bug.cgi?id=33550. 

Dialog owners are encouraged to migrate to the new behavior and delete any 
code previously used to persist size and location.  (Then all those pesky 
multi-monitor bugs won't be your fault anymore!).  It is still up to you to 
determine 
whether persisting location and/or size makes sense for your particular 
dialog.   
You won't magically get any behavior without doing something.   

Here's how it works. 

(1)  Override the method Dialog.getDialogsBoundsSettings() to return the 
IDialogSettings appropriate for persisting your dialog's bounds.   

(2)  If you want to persist the last known size and location of the dialog, 
you are done.  If you want to persist only the size or only the location, 
override the method Dialog.getDialogBoundsStrategy() to return the constant 
indicating what strategy to use.  This is a combination of bit mask values 
which are 
currently defined as 
  DIALOG.PERSIST_LOCATION - persist the last known location of the dialog 
  DIALOG.PERSIST_SIZE - persist the last known size of the dialog
Comment 1 Eclipse Webmaster CLA 2019-09-06 16:17:58 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.