Log In UI - Part 3

Illustrates how to use states to create a second UI page.

Log In UI - Part 3 is the third in a series of tutorials that build on each other to illustrate how to use Qt Design Studio to create a simple UI with some basic UI components, such as pages, buttons, and entry fields. Part 3 describes how to use states to add a second page to the UI. On the first page, users can enter a username and password to log in. On the second page, they can register if they do not already have an account.

Because the second page will contain most of the same UI components as the login page, you will use states to show and hide UI components as necessary when a user selects the Create Account button.

These instructions build on:

The Learn More sections provide additional information relevant to the task at hand.

Adding UI Components

You will add another text field for verifying the password that users enter to create an account and a back button for returning to the login page. You are already familiar with the tasks in this section from Part 1 and Part 2 of this tutorial.

To preview the changes that you make to the UI while you make them, select the (Show Live Preview) button on the Form Editor toolbar or press Alt+P.

To add the text field and a back button needed on the registration page to the Screen01 component:

  1. Open Screen01.ui.qml in Form Editor for editing.
  2. Drag-and-drop a Text Field from Library > Components > Qt Quick Controls to fieldColumn in Navigator.
  3. In Properties, change the ID of the text field to verifyPasswordField.
  4. In the Geometry group, Size field, set the width of the field to 300 pixels to match the size of the existing fields.
  5. In the Placeholder field, set the placeholder text to Verify password and mark the text translatable.
  6. Drag-and-drop a PushButton component from Library > Components > My Components to the root rectangle in Navigator.
  7. Select the button in Navigator and change its ID to backButton in Properties.
  8. In the Geometry group, Size field, set the button width to 40 pixels to create a small round button.
  9. In the Text field, enter <.
  10. In the Font group, Size field, set the font size to 24 pixels.
  11. Under Layout, select the (Top) and (Right) anchor buttons to anchor backButton to the top right corner of its parent with 20- and 10-pixel margins, respectively.
  12. Select File > Save or press Ctrl+S to save your changes.

Screen01 should now look something like this in the Design mode and live preview:

"Login page with new UI components"

Next, you will add states for the login page and the registration page, where you use the visibility property to hide the password verification field and the back button on the login page and the login button on the registration page.

Using States to Simulate Page Changes

You will now add states to the UI to show and hide UI components in the Form Editor, depending on the current page:

  1. In the States view, select Create New State.

    "States view"

  2. Enter loginState as the state name.
  3. Select verifyPasswordField in the Navigator, and deselect the Visibility check box in Properties to hide the verify password field in the login state.

  4. Repeat the above step for backButton to hide it, too.
  5. In States, select for loginState to open the Actions menu, and then select Set as Default to determine that loginState is applied when the application starts.
  6. With the base state selected, add another state and name it registerState. This state should now look identical to the base state.
  7. Select loginButton in the Navigator, and deselect the Visibility check box in Properties to hide the login button in the registration state.
  8. Select File > Save or press Ctrl+S to save your changes.

You can now see all the states in the States view. The live preview displays the default state, loginState:

"States view"

Learn More - States

The state of a particular visual component is the set of information which describes how and where the individual parts of the visual component are displayed within it, and all the data associated with that state. Most visual components in a UI will have a limited number of states, each with well-defined properties.

For example, a list item may be either selected or not, and if selected, it may either be the currently active single selection or it may be part of a selection group. Each of those states may have certain associated visual appearance (neutral, highlighted, expanded, and so on).

Youn can apply states to trigger behavior or animations. UI components typically have a default state that contains all of a component's initial property values and is therefore useful for managing property values before state changes.

You can specify additional states by adding new states. Each state within a component has a unique name. To change the current state of an component, the state property is set to the name of the state. State changes can be bound to conditions by using the when property.

Next, you will create connections to specify that clicking the Create Account button on the login page triggers a transition to the registration page and that clicking the back button on the registration page triggers a transition to the login page.

Connecting Buttons to States

Components have predefined signals that are emitted when users interact with the UI. The PushButton component contains a Mouse Area component that has a clicked signal. The signal is emitted whenever the mouse is clicked within the area.

You will now use Connection View to connect the clicked signal of registerButton to registerState and that of backButton to loginState:

  1. Select View > Views > Connection View to open the Connections tab.
  2. Select registerButton in the Navigator.
  3. In the Connections tab, select the button to add the action that the onClicked signal handler of registerButton should apply.
  4. Double-click the value Action column and select Change state to registerState in the drop-down menu.
  5. Repeat the steps above to connect backButton to loginState by selecting Change state to loginState in the last step.
  6. Select File > Save or press Ctrl+S to save your changes.

You can now see the following connections in the Design mode:

"Connections tab"

In the live preview, you can now click the Create Account button to go to the registration page and the back button to return to the login page.

Learn More - Signal and Event Handlers

UI components need to communicate with each other. For example, a button needs to know that the user has clicked on it. In response, the button may change color to indicate its state and perform an action.

A signal-and-handler mechanism is used, where the signal is the event that is responded to through a signal handler. When a signal is emitted, the corresponding signal handler is invoked. Placing logic, such as a script or other operations, in the handler allows the component to respond to the event.

For more information, see Signal and Handler Event System.

Next Steps

For a more complicated UI, you would typically use components that specify a view of items provided by a model, such as a List View or StackView. For more information, see Lists and Other Data Models.

To learn how to use a timeline to animate the transition between the login and registration pages, see the next tutorial in the series, Log In UI - Part 4.

Files:

Images:

Available under certain Qt licenses.
Find out more.