You can help by commenting or suggesting your edit directly into the transcript. We'll review any changes before posting them. All comments are completely anonymous. For any comments that need a reply, consider emailing training@inductiveautomation.com.
Version:
LESSON LIST
LESSON
Anatomy of a Window
Description
Windows are the top-level unit of design for Vision projects. Learn the basics of how a window is constructed.
Video recorded using: Ignition 8.1
Resources
Transcript
(open in window)[00:00] In this video, we will discuss the basic parts of a Vision Window. When creating something in Vision, it is merely a collection of Vision Windows coupled with a navigation scheme, by which you must move from Window to Window. When you first create a Window, it's given a name which must be a unique name among the Windows residing in the same folder. You can create folders to organize your Windows and it's actually strongly recommended to spend some time thinking about implanting the folder hierarchy for your Windows. Planning your folder structure ahead of time will make your life a lot easier as your project grows and starts consisting of more and more Windows. Windows are identified by their full path, not just their name. The full path of a Window starts with a root folder. Then each sub folder you must drill into to reach your Window and finally ends with the Window name.
[01:03] An example of this would be here, my Test Window. It starts with the root folder, which would be Vision Windows. Main Windows is the next folder I have to drill into and my Test Window resides within. So my full path to my Window here would be Vision Windows, slash Main Windows, slash Test Window. This is an important thing to remember because once you start setting up your own custom navigation schemes, if you decide to reorganize your Windows afterwards, all your references to your Windows will no longer be valid and you'll have to go back and re-reference where necessary. Now, if we're creating a Window here by right clicking and choosing Main Window, you'll see that this is automatically created with one component called Root Container. Every Window you create has a Root Container, and this cannot be deleted like other components you add to your Window. You can add a nest, other container components into the Root Container, but the Root Container is always the base container on your Window.
[02:09] Finally, let's examine the title bar and border properties. All of your Windows, no matter what type will have these properties. However, it doesn't always make sense to show a title bar on your Windows. My Test Window, if we go back there was created as a Main Window. Meaning it's supposed to be maximized and full screen. So you can see that by default, the border and title bar display policy had been set to Win not maximized. This means when the Window is maximized and acting like a Main Window, it shouldn't have a title bar or border. Many times, you'll want your pop-up Windows to show a border and title bar. With these settings, since a pop-up is maximized, you would get a title bar and a border on your Window. In the next videos, we will go into more detail on the different parts of a Vision Window.