My use case was re-purposing an existing PopupPanel. Sometimes I needed a modal, auto-hiding panel and other times I needed a non-modal, non-auto-hiding panel. There would only ever be one of these panels showing at any given time. It seemed most efficient in terms of Java code size, complexity, and performance to reuse a single PopupPanel instance (I didn't test for impact on performance or compiled JS code size).
On Mon, Oct 6, 2008 at 12:44 PM, Emily Crutcher <[EMAIL PROTECTED]> wrote: > +1 to > public boolean isAutoHideEnabled() > public boolean isModal() > > Why do we want to change whether auto hide/modality is enabled on an > existing popup panel? It seems like if we do this we would need to check > for edge cases that currently don't come up. > > > On Mon, Oct 6, 2008 at 12:09 PM, Alex Rudnick <[EMAIL PROTECTED]> wrote: > >> >> +1, sounds like a good idea. >> >> On Mon, Oct 6, 2008 at 11:54 AM, Jason Essington >> <[EMAIL PROTECTED]> wrote: >> > +1 here, as I've recently had to use the violator pattern to flip those >> > bits. >> > -jason >> >> -- >> Alex Rudnick >> swe, gwt, atl >> >> >> > > > -- > "There are only 10 types of people in the world: Those who understand > binary, and those who don't" > > > > --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
