Your browser does not support JavaScript
Exit Print View

Lightweight UI Toolkit Developer’s Guide

Get PDF Book Print View

Document Information


1.  Introducing the Lightweight UI Toolkit Library

2.  Using Lightweight UI Toolkit Widgets

3.  Using Lists

4.  Table and Tree

5.  Using Dialogs

5.1 Dialog Types

5.2 Creating a Dialog

5.2.1 Return Types of Show Methods

5.2.2 Non-Static Show Methods

5.2.3 Using the dispose() Method

5.2.4 Getting the User's Input from a Dialog

6.  Using Layout Managers

7.  Painters

8.  Using the Style Object

9.  LWUIT Implementation

10.  HTMLComponent

11.  Theming

12.  Resources

13.  Using Transitions and Animations

14.  M3G

15.  Logging

16.  Authoring Components

17.  Portability and Performance



Chapter 5

Using Dialogs

A Dialog is a form that occupies a part of the screen as a top level component. By default dialogs always appear as a modal entity to the user. Modality indicates that a dialog blocks the calling thread even if the calling thread is the Event Dispatcher Thread (EDT). Dialogs allow us to prompt users for information and rely on the information being returned as a response after the dialog show method. Each Dialog has a body that is located in the center of the dialog. The Body can contain a component, so you can use your own customer component or pre-built container.

Note - A modal dialog does not release the block until a dispose method is called. For example, calling show() from another form does not release the block.

5.1 Dialog Types

For better user experience, dialogs have five types of alerts. The alert type indicates a sound to play or an icon to display if none is explicitly set:

By default the alerts are set to play the device alert sounds.

Icons are not currently provided by default, but you can manually add them to customized dialogs. Icons can be used to indicate the alert state, similar to JDialog icons in Swing. See

5.2 Creating a Dialog

To create and show a dialog you can do the following:

The arguments to all of the show methods are standardized, though the number of arguments for each method varies. The static show methods provide support for laying out standard dialogs, providing icons, specifying the dialog title and text, and customizing the button text.

The following list describes each argument. To see the exact list of arguments for a particular method, see the Dialog API in the API documentation located in install-dir/docs/api/lwuit.

String title

The title of the dialog

Component body

Component placed in the center of the dialog. This component can be a container that contains other components.

String text

The text displayed in the dialog which can be used instead of Body.

Command[] cmds

Array of commands that are added to the dialog. Any click on any command disposes of the dialog. Examples of commands are OK and Cancel.

int type

The type of the alert can be one of TYPE_WARNING, TYPE_INFO, TYPE_ERROR, TYPE_CONFIRMATION or TYPE_ALARM to indicate the sound to play or an icon to display.

Image icon

The icon to display in the dialog.

long timeout

A timeout in milliseconds, after which the dialog closes and null is returned. If time-out value is 0, the dialog remains open indefinitely, until its dispose method is invoked.

Transition transition

The transition installed when the dialog enters and leaves the screen. For more information see link icon13.3 Transition.

String okText

The text to appear in the command dismissing the dialog.

String cancelText

Optionally null for a text to appear in the cancel command for canceling the dialog.

int top

Inset in pixels between the top of the screen and the form.

int bottom

Inset in pixels between the bottom of the screen and the form.

int left

Inset in pixels between the left of the screen and the form.

int right

Inset in pixels between the right of the screen and the form.

boolean includeTitle

Whether the title should hang in the top of the screen or be glued onto the dialog content pane.

5.2.1 Return Types of Show Methods

You can use one of three convenient return value show methods: void, Command, or boolean.

5.2.2 Non-Static Show Methods

The dialog API provides two non-static methods to create two more types of dialogs.

The first method takes no arguments and produces a dialog without any commands. The only way to close such a dialog is to invoke the dispose() method on the dialog. Since the dialog is blocking, meaning once the dialog is displayed its calling thread can not proceed until it is closed, the call to dispose must be made from a different thread. To do this, schedule the call to dispose with a timer thread. Note that the timer thread must be started before the dialog is displayed. This approach is referred to as an auto-closing dialog.

The second dialog type has five parameters. The first four are the four wing insets (top, bottom, left, and right) and the fifth parameter determines whether to include the Dialog title assigned through the dialog constructor (see link iconTypical Dialogs).

// Call show with inset parameters, 90, 10, 10, true);

5.2.3 Using the dispose() Method

The dispose methods closes the current dialog and returns to the parent form. When show() is used without arguments, one way to close the dialog is to set a timer to call dispose just before calling the show method (otherwise the dispose method is never performed).

5.2.4 Getting the User's Input from a Dialog

As mentioned in link icon5.2.2 Non-Static Show Methods, return value types can be either Command or a boolean value. For example, if a user has a dialog with two commands, Approve and Decline, the user clicks and the selected command is returned. For the boolean return type, a true or false value indicates whether the user clicked the OK command.

Typical Dialogs
Dialogs are OK Cancel, Info, Non-static show() and Dialog with insets