Child pages
  • Windows and Dialogs

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

Dialogs can be either modal or non-modal (also referred to as modeless). A modal dialog blocks access to all other dialogs and the window in it's parent hierarchy, whereas non-modal dialogs do not block the access.

In the Smart Client, if run under Java 5, the modal dialog will block all windows and dialogs, not only the ones in it's parent hierarchy. See #Smart Smart Client modal dialog behavior difference in Java 5 & Java 6 for more info.

In the Smart Client the call that shows the modal dialog is blocking, meaning that it will not continue until the modal dialog is closed. Only when the dialog is closed will the rest of the code in the function that showed the modal dialog be executed.

In the Web Client the call that shows the modal dialog in non-blocking, meaning it will return immediately and the rest of the code in the function will continue to execute. 

...

  • The JSWindow class: the main class for managing windows and dialogs displaying Forms in Servoy
  • plugins.window: a plugin that provides access to the MenuBar, ToolBars and Status bar in the Smart Client and allows to create custom keyboard shortcuts in both the Smart and Web Client
  • plugins.dialogs: a plugin that provides functions to show a number of simple dialogs. This plugin is only supported in the Smart Client
  • The controller object of Forms:
    • controller.getFormContext()
    • controller.getWindow()unmigrated-wiki-markup
    • controller.show(\[windowName\])
    • Wiki Markupcontroller.showRecords(data, \ [windowname\])
  • The Application class:
    • application.closeAllWindows()
    • application.createWindow()
    • application.getScreenHeight()
    • application.getScreenWidth()
    • application.getWindow()
    • application.isFormIndialog()
    • application.showForm???
    • application.setToolbarVisible()