Using the Navigation Manipulator

Use the Navigation Manipulator to set the keyboard keys that the user can use to navigate to different directions in your application.

Default directional navigation keys

These are the default directional keyboard keys that the user can use in a Kanzi application:

• The Slider nodes have the Focusable property enabled and are focusable by default. When a Slider node has focus, to move the knob of that slider, you can use these default keyboard keys:

  • Home to move the slider knob to the beginning of the rail

  • End to move the slider knob to the end of the rail

  • ← and → to move the knob of a horizontal slider

  • ↑ and ↓ to move the knob of a vertical slider

  To move a slider knob with the arrow keyboard keys, in that Slider node set the amount that the knob moves for each key press with the Step Value property.

• The Scroll View nodes have the Focusable property enabled and are focusable by default. When a Scroll View node has focus, to scroll that node, you can use the default keyboard keys ←, →, ↑, and ↓.

• When a Grid List Box node has focus use these keyboard keys:

  • ↑ and ↓ to scroll the list items in a vertical list box

  • → and ← to scroll the list items in a horizontal list box

  • Home to select the first list item

  • End to select the last list item

  • Page Up and Page Down to go to the beginning and end of the visible area of a list box

• When a Text Box node is in the editing state, to move the cursor in that text box, you can use these default keyboard keys:

  • ← to move the cursor one character backward.

  • → to move the cursor one character forward.

  • Ctrl ← to move the cursor to the word boundary that precedes the cursor.

  • Ctrl → to move the cursor to the word boundary that follows the cursor.

  • Home to move the cursor to the beginning of the text content.

  • End to move the cursor to the end of the text content.

  When a Text Box node is in the editing state, to modify the text selection in that text box, you can use these default keyboard keys:

  • Shift ← to move the active cursor in the text selection one character backward.

  • Shift Ctrl to move the active cursor in the text selection to the word boundary that precedes the current position.

  • Shift Home to move the active cursor in the text selection to the beginning of the text content.

  • Shift → to move the active cursor in the text selection one character forward.

  • Shift Ctrl → to move the active cursor in the text selection to the word boundary that follows the current position.

  • Shift End to move the active cursor in the text selection to the end of the text content.

  • Ctrl A to select all text.

Using the Navigation Manipulator triggers

Use the Navigation Manipulator triggers to react when the user starts, finishes, or cancels a directional navigation key gesture. For example, you can use a specific key to enable the user to move the keyboard focus in a specific direction.

The Navigation Manipulator has these triggers:

• Key Navigation Started trigger is set off when Kanzi recognizes the key-pressed or key repeat gesture for a navigation key.

  For example, this happens when the user presses a navigation key on their keyboard.

• Key Navigation Finished trigger is set off when Kanzi recognizes the key-released gesture for a navigation key.

  For example, this happens when the user releases a navigation key on their keyboard.

• Key Navigation Canceled trigger is set off when Kanzi recognizes the cancellation of the key-pressed gesture for a navigation key.

To use the Navigation Manipulator triggers:

1. Create and configure a Navigation Manipulator:

   1. In the Node Tree or Prefabs select a focusable node that you want to receive directional navigation input from keyboard keys. See Using focus.

      Tip

      The Button, Toggle Button, Scroll View, Slider, and Text Box nodes have the Focusable property enabled and are focusable by default.

      For example, in the Prefabs select a prefab that you use to instantiate a vertically stacked group of menu buttons. You can by default move the focus between the buttons in the forward direction by pressing the Tab key and in the backward direction by pressing the Shift Tab keys. See Moving focus in the focus chain and Showing when a user interface element has focus.

      

   2. In the Node Components press Alt and right-click Input Manipulators, and select Navigation Manipulator.

      You use the Navigation Manipulator to set a node to react to directional navigation input from one or more keyboard keys.

      

   3. In the Navigation Manipulator add and set one or more navigation key properties to the keyboard keys to which you want the node to react.

      For example, to configure the keyboard keys with which the user can navigate up and down, add and set the Up Navigation Key and Down Navigation Key properties.

      

2. Create and configure the trigger for a navigation key that you set in the previous step in the Navigation Manipulator:

   1. In the Node Components create one of the Navigation Manipulator triggers.

      For example, in the Node Components press Alt and right-click Triggers, select Message Trigger > Key Navigation Started, and name the trigger.

      

   2. If you set more than one navigation key property in the Navigation Manipulator, use a trigger condition to configure which navigation key sets off the trigger that you created.

      In the Node Components press Alt and right-click the trigger, select Trigger Condition, and in the condition set:

      • A

        • Type of A to Message argument

        • Message Argument to Navigation Direction

      • Operation to =

      • B

        • Type of B to Fixed

        • Fixed Value to the navigation direction to whose navigation key you want the trigger to react.

          For example, if you want the trigger to set off when the user presses the key that you set in the Navigation Manipulator using the Down Navigation Key property, set Fixed Value to Down.

      

   3. In the Node Components press Alt and right-click the trigger that you created and select the action that you want the trigger to execute when the user presses the navigation key that you configured in the Navigation Manipulator.

      For example, select the Move Focus action and in the action settings set Direction to Forward.

      This action moves focus to the next node in the focus chain in the forward direction, similarly to how the focus moves when the user presses the Tab key.

      

   When the user presses down the key that you set in the Navigation Manipulator, the Key Navigation Started trigger sets off the action that you created.

   In this example, when the user presses down the ↓ (Arrow down) key that you set in the Navigation Manipulator in the Down Navigation Key property, the focus moves to the next menu button in the forward direction.

   

3. Repeat the previous step to create and configure another Navigation Manipulator trigger.

   For example, create another Key Navigation Started trigger and in that trigger create:

   • Trigger Condition to set off the trigger when the user presses the key that you set in the Navigation Manipulator using the Up Navigation Key property.

   • Move Focus action where you set Direction to Backward.

   In this example, when the user presses down the ↑ (Arrow up) key that you set in the Navigation Manipulator in the Up Navigation Key property, the focus moves to the next menu button in the backward direction.

   

You can set more navigation keys in the Navigation Manipulator and create triggers that define what happens when the user presses those keys.

For example, in the Navigation Manipulator set the End Navigation Key property and create a Key Navigation Started trigger with a Try Set Focus action that sets focus to the last button in the group when the user presses the End key.

Using the navigation manipulator in the API

For details, see the NavigationManipulator class in the Kanzi Engine API reference.

See also

Handling user input

Using focus

Using the Key Manipulator

Using triggers

Tutorial: Move focus in an application