UIs are designed to present different UI configurations in different scenarios, or to modify their appearances in response to user interaction. Often, there are a set of changes that are made concurrently, such that the UI could be seen to be internally changing from one state to another.
This applies generally to UIs regardless of their complexity. A photo viewer may initially present images in a grid, and when an image is clicked, change to a detailed state where the individual image is expanded and the interface is changed to present new options for image editing. At the other end of the scale, when a button is pressed, it may change to a pressed state in which its color and position are modified so that it appears to be pressed down.
Any component can change between different states to apply sets of changes that modify the properties of relevant components. Each state can present a different configuration that can, for example:
- Show some UI components and hide others.
- Present different available actions to the user.
- Start, stop, or pause animations.
- Execute some script required in the new state.
- Change a property value for a particular component.
- Show a different view.
You can animate transitions between states in Transition Editor.
You can create states in the States view, by selecting Create New State.
For example, to change the appearance of a button, you can hide the button image and show another image in its place. Or, to add movement to the view, you can change the position of a component in Form Editor and then add animation to the change between the states.
The properties that you change in a state are highlighted with blue color. In Text Editor, you can see the changes recorded as changes to the base state.
For more information, watch the following video:
To determine the startup state of the application, select to open the Actions menu, and then select Set as Default.
To reset the state later, select Actions > Reset Default.
To determine when a state should be applied, select Actions > Set when Condition. In Binding Editor, specify a when property for the state. Set the value of the property to a boolean expression that evaluates to
true when you want the state to be applied.
This enables you to evaluate the truthfulness of several components' properties and move the UI to the state in which these conditions apply. You can evaluate whether something is true or false, greater than or equal to something else, and so on. You can also use operators, such as AND or OR, to evaluate the truthfulness of several components.
The when conditions are evaluated from left to right and in order of appearance in the code. Therefore, if you have two conditions for two different states that both evaluate to
true, the first state is applied.
In Binding Editor, select the component and property to create the expression. For example, to change the state when a button is pressed, you could select a button component and its pressed property.
When you compose the expressions in Binding Editor, the code completion feature lists the components and their properties you can use in the expressions.
You can use the following logical operators in the expressions to combine several conditions in one expression:
|Operator||Meaning||Evaluates to |
|!||NOT||The condition is not met.|
|&&||AND||Both conditions are met.|
|||||OR||Either of the conditions is met.|
|<||Less than||The left operand is less than the right operand.|
|>||Greater than||The left operand is greater than the right operand.|
|>=||Greater than or equal||The left operand is greater than or equal to the right operand.|
|<=||Less than or equal||The left operand is less than or equal to the right operand.|
|==||Equal||The operands are equal.|
|===||Strict equal||The operands are equal and of the same type.|
|!=||Not equal||The operands are not equal.|
|!==||Strict not equal||The operands are of the same type but not equal, or are of different type.|
Alternatively, you can use And Operator, Or Operator, and Not Operator components to bind property values using the boolean AND, OR, and NOT operator. For more information, see Logic Helpers.
In addition, you can use arithmetic operators to compare numbers before checks. However, we recommend that you create separate properties for this purpose whenever possible.
To apply a state to a button when the button is pressed, you could simply write:
To apply a state when the button is not pressed, select the NOT check box.
To apply a state when the button is not pressed, selected, nor hovered on, you could combine conditions, as follows:
when: !control.pressed && !control.checked && !control.hovered
To apply a state when the button is pressed or selected, but not hovered on, you could write:
when: control.pressed || control.checked && !control.hovered
To keep the code clean, you should create a base state that contains all the components you will need in the application. You can then create states, in which you hide and show a set of components and modify their properties. This allows you to:
- Align components on different views with each other.
- Avoid excessive property changes. If a component is invisible in the base state, you must define all changes to its child components as property changes, which leads to complicated code.
- Minimize the differences between the base state and the other states to keep the code short and readable and to improve performance.
- Avoid problems when using transitions and animation when changing states.
To create views for an application by using states:
- In the base state, add all components you will need in the application (1). While you work on one view, you can click the icon in Navigator to hide components on the canvas that are not part of a view.
- In States, select Create New State to create a new state and give it a name. For example,
- In Properties (2), deselect the Visibility check box or set Opacity to 0 for each component that is not needed in this view. If you specify the setting for the parent component, all child components inherit it and are also hidden.
- Create additional states for each view and set the visibility or opacity of the components in the view.
- To determine which state is applied when the application starts, select Actions > Set as Default.
Available under certain Qt licenses.
Find out more.