In this lesson we'll discuss Visual Hierarchy, which is the treatment and arrangement of objects in order to effectively communicate information.

Tags are points of data and may have static values or dynamic values that come from an OPC address, an Expression, or a SQL query. The values can be used on screens and in Transaction Groups. Additionally, Tags offer a core set of features above and beyond simple values, such as scaling, alarming, and

Property Binding is perhaps the most important concept to understand when designing a project using the Vision module. It is primarily through property bindings that you bring windows to life, and have them do useful things. A property binding simply links one component's property to another on the same

A Quality Code represents a level of confidence in a value. Quality codes are made up of a level (Good, Bad, Error, or Uncertain) and an integer. If a value's quality is not Good, the value generally should not be trusted.

Pages are the main method of navigation in Perspective. When talking about pages, there are two distinct objects to be aware of.

Each Perspective component has a unique set of properties that can be set and modified within the Perspective Property Editor. A component property is simply a named variable with a distinct type that affects something about the component's behavior or appearance, such as size, color, name, visibility

UDTs (User Defined Types), also referred to as Complex Tags, offer the ability to leverage object-oriented data design principles in Ignition. UDTs are extremely important in Ignition. With UDTs, you can dramatically reduce the amount of work necessary to create robust systems by essentially creating

The Ignition Designer is where the majority of configuration and design work is done. The Designer uses web-launch technology to open and edit your projects. This is how you can configure your Perspective and Vision projects.

Cognitive load represents the amount of working memory in a person. If a design is more complex in nature, then it can have a higher cognitive load, which results in poorer overall experience for the user. In this lesson we'll learn how to minimize cognitive load in our designs.

To create some instances of our Data Card, we'll get acquainted with the Flex Repeater, which allows us to create a bunch of instances all within a single component.