Note: This topic is about popup windows. It does not refer to popup menus. For more information to popup menus, go to Popup Menu.
Popups are created by pick actions or commands configured with:
a command of Load Display or Load Graphic Display
one of the targetTypes
Popups work in the following platforms:
There are five different target types.
Popup Window (Display Dependent) / Popup
Popup Window (Display Dependent - Modal) / PopupModal
Popup Window (Window Dependent) / WindowOwnedModalPopup
Popup Window (Window Dependent - Modal) / WindowOwnedModalPopup
Popup Window (Independent) / UnownedPopup
The first in each pair is for local commands, the second for global commands. The pairs should be equivalent.
The target type determines how the popups work. They work differently based on your platform.
Target type is the type of window to be opened. Some of these selections are window types, some are windows hierarchy (relative paths), and some are absolute settings (such as the Root window). For more information about windows, refer to Windows Dynamics.
The targetType parameter is used in conjunction with the targetName parameter to designate which display window to open into.
TargetName is the actual window to be opened. Click the ellipsis button [...] to open the Data Browser so you can identify the target.
If target type is Self: (targetName is unused)
Loads the display into the current window.
This is the default target type.
If target type is WindowOwnedPopup:
If targetName is specified and there is already an open popup window that matches that name (and is owned by the current window), the display is loaded into that popup window.
If targetName is specified and there is NOT already an open window that matches that name (and is owned by the current window), the display is loaded into a NEW popup window with the name specified by TargetName.
If targetName is NOT specified, the display is loaded into a NEW unnamed popup window.
Window owned popups will always stay above the owner window and will be minimized when the owner window is minimized. Window owned popups remain open even if the display is changed in the owner window. Window owned popups will be automatically closed when the owner window exits runtime or is closed.
If the target type is DisplayOwnedPopup:
It is the same as WindowOwnedPopup except the popup is owned by the Display (meaning, if a new is loaded in a given window, all popups owned by the display that is being replaced, are automatically closed).
If target type is DisplayOwnedModalPopup:
It is the same as DisplayOwnedPopup except the popup is "modal" (disables parent window).
If target type is WindowOwnedModalPopup:
It is the same as WindowOwnedPopup except the popup is "modal" (disables parent window).
If target type is UnownedPopup:
It is the same as WindowOwnedPopup except the popup is "unowned" (they are owned by the desktop). Unowned popups will not necessarily stay above the window that opened them. Unowned popups remain open even if the display is changed in the window that opened them. Unowned popups will be automatically closed when the "root" window exits runtime or is closed.
If target type is Embedded:
It is the same as DisplayOwnedPopup except the window is an embedded child of its parent.
If target type is Parent:
If targetName is specified and there is a parent window in the parent chain that matches the name, the display is loaded into that parent window.
If targetName is specified and there is NOT a parent window in the parent chain that matches that name, the behavior is the name as Self.
If targetName is NOT specified, the display is loaded into the first parent window (starting at the current window) in the parent chain.
If there is no parent, the behavior is the same as Self.
If target type is Root: (targetName is unused)
The display is loaded into the topmost (root) parent window in the parent chain.
If there is no parent, the behavior is the same as Self.
IE-based WebHMI works identically to GraphWorX64 application.
There are two types of popups - independent and dependent.
Dependent popups in HTML5 WebHMI were first introduced in version 10.97.1. Prior to them, HTML5 only had independent popups. They are limited in the functionality and cannot support features that GraphWorX64 popups have.
If you upgrade from an earlier version to 10.97.1 or later and you prefer independent popups to dependent popups, you will need to change your popup type to keep using independent popups.
It is possible to manually switch popups back to the independent type and keep the full compatibility with 10.97.
iOS and Android applications do not support popups. Any of the five popup window target types will load a new display (as if the target type of "Current Display" was chosen).
See Also: