Hide the current showing dialog and show the next dialog in the queue (if any).
Display a component dialog on the screen. A component dialog is a dialog allowing you to display your own custom dialog by specifying
a component type being displayed as its body. That component type must be a class which is an instance of
IDialogController.
A dialog model being displayed.
The promise which will be resolved when this dialog is closed. The resolving result will be the value returned
from IDialogController.getDialogResult method.
Display a confirmation dialog on the screen.
The dialog title text.
The dialog message which will be displayed in the dialog body.
To display the CANCEL button or not. By default, the confirmation dialog will contain only
YES and NO button.
The css "width" style value governing dialog width e.g. 100px, 50pt.
The css "height" style value governing dialog height e.g. 100px, 50pt.
The promise which will be resolved when this dialog is closed. The resolving result will be the value
returned from ConfirmDialog.getDialogResult method.
Show current dialog described by the currentModel. This usually be the last model generated by
the last show...Dialog method call.
Display a message dialog on the screen.
The dialog title text.
The dialog message which will be displayed in the dialog body.
The css "width" style value governing dialog width e.g. 100px, 50pt.
The css "height" style value governing dialog height e.g. 100px, 50pt.
The promise which will be resolved when this dialog is closed. The resolving result will be the value
returned from MessageDialog.getDialogResult method (which always returns true).
Generated using TypeDoc
A
singletonUI component controllingapplicationpop-up dialog logic. This dialog is amodaldialog, saying that, when it is displayed, all user's UI actions will be blocked and the user will be forced to focus on this dialog. When the user completes the interaction with this dialog, for example, clicking on "OK" button, this dialog will be hidden and the user can resume normal UI operations. Normally, you should NOT directly access this component instance but you could control it via DialogService.Please note that there is a dialog
display queueoperating behind the scenes. Thisdisplay queueis aFIFOqueue keeping all dialog models (DialogModel) --which are automatically generated and kept in the queue whenshow...Dialogmethods are called-- but those dialog models cannot be displayed suddenly. For example, if there already is a dialog being displayed currently, but, there is also someone else callingshow...Dialogmethod simultaneously, the dialog model generated from the latershow...Dialogmethod will not be showed suddenly. Nevertheless, it'll be showed immediately when the first dialog is closed. For this mechanism, the dialog model can be firstly kept in the queue, then, it will be showed and removed from the queue when its preceding dialog is closed.If you want to implement your own custom dialog, you should do it using
component dialograther than building it all up from scratches. The only thing which you need to do is just implementing the component being displayed inside the dialog body. All other mechanisms, such as dialogdisplay queuelisted above, should be left to be handled by the framework or by this class. For more information about building custom dialog, please see showComponentDialog.shiorin, tee4cute
DialogService