Community
Participate
Working Groups
Look at subclasses of WizardDialog and you'll see plenty of subclasses that exist only to provide the dialog bounds settings so that size/location of a wizard will be persisted. It might be better if WizardDialog added API so that clients could set the dialog bounds settings and bounds strategy, similar to what we do in SelectionDialog.
What's extra bogus about this is that it has potential API effects on components who want to let clients open their wizards. The client has to have access to the wizard dialog subclass or else some helper, or else implement their own.