More specifically - all windows can be closed programmatically (via the close()
method), but not all frame skins are guaranteed to provide a UI means for doing
so. The same applies to maximize, minimize, etc. Making this a style still
allows the caller to set it, but doesn't tie any particular theme
implementation to a strict window management API.
On Monday, October 26, 2009, at 08:39PM, "Greg Brown" <[email protected]> wrote:
>You can set the "showCloseButton" style to false. This is a style rather than
>a property because not all frame trim will necessarily include a "close"
>button.
>
>On Monday, October 26, 2009, at 08:12PM, "Christopher Brind"
><[email protected]> wrote:
>>Hi,
>>
>>I've created a Dialog which I don't want the user to be able to close
>>as it is a splash screen that shows my application is initialising.
>>
>>I've added a WindowStateListener which overrides the previewClosed()
>>method and returns Vote.DENY which does the trick:
>>
>> splash.getWindowStateListeners().add(new
>> WindowStateListener.Adapter() {
>> @Override
>> public Vote previewWindowClose(Window window) {
>> return Vote.DENY;
>> }
>> });
>> splash.open(display, window, true, null);
>>
>>
>>However, I'd actually like to remove the 'close' dialog button all
>>together since I plan on closing it programmatically once the
>>application is ready to go.
>>
>>I was hoping to find a 'closeable' attribute on the Dialog, but no
>>such luck. I tried a Frame, but that has even more title bar
>>furniture and isn't centred.
>>
>>I can see that this stuff is handled in the skin but ... there be
>>dragons - do you think title bar 'furniture' control should be part of
>>the API / WTKX (e.g. closeable, maximisable, minimizable attributes) -
>>or am I missing something?
>>
>>Any ideas / suggestions?
>>
>>Cheers,
>>Chris
>>
>>
>
>
