Skip to main content
Version: 7.9


Using Windows

Windows are the gateway to your HMI/SCADA application. A project is a collection of windows which are the basic building blocks for all your screens, and a hierarchy of components that users interact with. When you publish your project, these windows are loaded into the Vision Client where any number of windows can be opened at one time. Your windows are brought to life through the property bindings and event handlers on your components. With the power of windows, they can be designed to be very sophisticated and complex, displaying lots of information, and yet very easy to use. The possibilities are endless when designing windows for your project.

In this Realtime Display example, you can see how windows can be used to display and interact with data and tags.

Windows - Ignition Demo

Working with Windows

Working with Windows is super easy! Windows are the top-level unit of a design for your project. There are three different window types: Main, Popup, and Docked. Each window type behaves differently as you can see here, and can be arranged any way you like.

Working with Windows - New Window Types

You can change a window's properties to behave differently, transforming the window into various configurations. You can create and re-use windows inside of Ignition. Passing custom parameters into windows allows you to create it once and re-use your screens. You can set windows to open once, or create popup windows with multiple instances so users can compare live values.

To create a window, all you need to do is select a window type, drag some tags to your window, and select the components you want to use. Next, change the default window properties to define the look and feel of the window, and set the behavior of the window. You can change window properties in the Property Editor as shown below or from the Project Browser. You can also organize your window into folders, rename them, add notes about your windows for others to see, import and export windows, and add security on your windows. To learn more, go to Working with Vision Windows.

New Window - MenubarWindow Property Editor
Working with Windows - MenubarWorking with Windows - Property Editor

Root Container

Inside a window there is always a Root Container. The Root Container is where you place all components in the window. This is a normal Container component except that it cannot be deleted or resized, and is always set to fill the entire window.

Titlebar and Border

A window can display a Titlebar and/or a Border. A titlebar allows you to drag a window around the workspace, and contains the window's close, maximize and restore buttons. The border of a window also lets you resize the window when it is floating or docked. Whether or not the titlebar and border are displayed depends on the property values set for your Titlebar and Border properties. A window typically displays both a titlebar and border when it is floating, but only a titlebar when maximized. It is often desirable to remove titlebars and borders on maximized windows.

For more information on Titlebars, Borders and Root Container refer to Window Properties.

Setting up a navigation strategy allows you to navigate between different windows in the runtime Client. To help you select the right strategy that fits your project structure, the Navigation Windows section provides a description of each navigation strategy and things to consider for determining the best navigation strategy for your facility. You can select from any of the following types of runtime navigational strategies when designing your Ignition project.

A typical navigation strategy for a Vision project is as follows:

  • Have a Docked window or two, usually docked North and/or West.
  • Have a single Main window visible at a time.
  • Use swap navigation to swap between the Main windows. This ensures that only one main window is open at a time.
  • Use standard open navigation to open various Popup windows as necessary.

This style of project is so common, that the default operation of the Tab Strip component expects it. When it is in its default automatic operation, it expects that each tab represents a "screen" window, and will automatically swap from the current screen to the desired screen.

Furthermore, the [System]/Client/User/CurrentWindow tag is calculated based on this strategy: its value is the name of the current maximized window. This navigation strategy is used in the Ignition Public Demonstration that you can download from our website.

To learn more, refer to Navigation Window.

Windows - Navigation Strategy

Popup windows are often opened by components in a main window and are meant to be on top of the screen. You can make a popup window as big or small as you want. It is useful to create a popup window for displaying additional information about a selected item on the screen. Windows can act as popups or drill down to show more information about anything you want.

Windows - Popup Windows

The great thing about all windows is that they can be parameterized so they can be re-used. For example, a parameterized popup window can display graphical historical information related to the Tags of your components, like a Tank. One popup window design can be re-used for many tanks as long as the proper information is passed to the popup window. Once you define a Custom Property on your popup window, your window can use it to show values based on whatever is in that property. Refer to Parameterized Popup Window for more information.

Windows - Popup Windows Tank 100

Windows - Popup Windows Tank Details