Navigation:  How to Work with Screens > Setting Screen Properties

 

Overview

 

Once a screen is added (see Creating and Editing a Screen), the properties window automatically appears. This is where the screen settings are defined. This properties window can be opened at any time during project development so you can edit the corresponding screen settings.

 

 

Setting of Screen Properties

 

To open the screen's properties window:

 

•right-click the screen's tree view representation and select "Edit",

 

OR

 

•open the screen by double-clicking it, in the tree view, and, then, double-click the open screen to access the screen properties window

 

OR

 

•right-click the screen and select "Edit".

 

 

"General" tab

 

The properties window opens with the "General" tab. Below are all the options displayed in this tab. You must adjust or maintain the options/values that are provided.

 

 

 

Detail of the "Select a Wallpaper" window

 

 

This window opens when you click in the options concerning wallpaper.

The "Theme" tab is open by default and contains the available wallpapers (the same that are displayed in the "Style Preview Section" when you select in the "Control" tab).

Select the adequate theme and click .

 

Detail of the Screen Toolbar

 

 

Below are icons that can be displayed in the toolbar of your device's screen.

 

 

 

Details on the "Color" window

 

 

You can customize the "Basic Colors" by changing the values of the available color elements (Hue, Sat, Lum, Red, Green and Blue).

 

"Help" tab

 

Another tab in the “Screen Properties” window is the “Help” tab. It is used to add text in a "help" format.

 

 

Entering data in the upper box adds information to the project's user report which is created by the "Report Settings" tool (located in the "File" menu > "Report").

Entering data in the lower box, is a text addition to the device itself, a "help" text that is viewed by the operator when he clicks in the screen's toolbar.

 

 

Use the right click in MCL-Designer's input boxes to access certain features regarding the input box's option as well as general actions such as "Copy"; "Paste"; "Search".

Ex: If you right-click the "Text Data" input box (included in a "Display Text" properties window), you are provided with the "Paste", "Search..." and "Variable Select" options.

If you right-click any other input box, it will provide other possibilities.

 

 

 

"Actions" tab

 

The final tab in the “Screen Properties” window is the “Actions” tab. It is used to add processes to actions that handle data within the screen.

 

 

 

Actions associated to Screens

 

There are very specific actions (ex: an operator validating his inputs, a barcode scan) that trigger the execution of something within the application, meaning, the execution of processes. These processes are defined by the developer.

The following types of actions can be associated to screens:

 

1. Ready

This action is executed after the "Routine In" and/or the display of screen controls and, immediately, before the operator begins to interact with the application.

 

2. Timer

This action is an exception. It is executed due to a lack of activity by the operator during a specific time cycle. It is associated to a specific process - a background "Go To" Branch process on a countdown timer. A specific countdown time and a target location can be set. This countdown can be redundant if the “Repeatable” option is checked.

 

If you use a "Timer" action on a screen, do NOT add "Timer" actions to any controls included in that same screen.

 

 

3. Barcode

This action is used to enable the device's barcode reader and read barcodes, at screen level, without the use of an Input Barcode control. The data being read via this action are stored in a local variable - L_Value (&1a).

When a "Barcode" action is added to a screen, you must define the related settings in its properties window:

 

 

a. Select the appropriate scanner profile for the "Barcode" action in the "Profile" drop-down.

 

 

As an alternative, click to access a table with a list of the available barcode profiles to choose from.

Once you access the barcode profiles table, you can also edit its profiles. See To Edit a Barcode Scanner Profile.

 

b. Check the "Auto Trigger" option, if you want the device to, automatically, activate its scanner and read a barcode when the application's workflow reaches the "Barcode" action (when the screen is loaded).

 

When using the "Barcode" action in a screen, consider the following:

 

•The operator can scan multiple barcodes without the screen having to reload after every barcode reading.

•If the "Auto Trigger" option is checked, when the screen is loaded/its workflow executes, the device's barcode reader (the beam) is activated automatically.

•If one of the controls in the screen is on focus (all control types except an Input Barcode), the action will execute anyway without affecting the control on focus.

 

We do NOT recommend the simultaneous use of Input Barcode controls and the "Barcode" action in the same screen.

If you have an Input Barcode and the "Barcode" action in the same screen and the control is on focus, the Input Barcode has the priority. Meaning, when the operator first presses the trigger, the data is captured by the Input Barcode control. When the operator presses the trigger again, it will execute the "Barcode" action.

 

•The beep is only triggered AFTER the whole code is executed so the operator knows that the scanner engine is ready for the next barcode read.

 

We recommend that the processes included in the "Barcode" action be as simple as possible, meaning, use processes that do not take long to execute so the scanner is more readily available for the next scan.

 

This action uses predefined Local Variables to store the barcode data being read:

 

 

4. RFID

This action is triggered after every RFID tag read. It is used to obtain the data on each tag and to store it in a pre-established variable. See The RFID action.

 

5. NFC

This action is triggered after every NFC tag read.

When an "NFC" action is added to a screen, you must define the related settings in its properties window:

 

 

a. Select the intended NFC profile in the "Profile" drop-down OR  click to access a table with a list of the available NFC profiles and select one. If required, you can also edit an existing profile or create more. See To Create an NFC Profile.

 

6. Hotkey

This action is used to define an action that is executed following a specified keystroke (in a virtual (SIP) or hardware keyboard).

This action can be used simultaneously in a screen and in one or more controls, so, it is important to understand how the system will handle "Hotkey" action priority. The "Hotkey" actions will be triggered as follows:

 

1. The "Hotkey" action associated to a control when it comes into focus (ex: a Hotkey defined by the developer within a Grid control which triggers a specific process/action).

2. The use of embedded keys within the control with focus (ex: navigating the fields of a "Grid" control with the use of arrow keys).

3. The "Hotkey" action associated to the screen that contains the control with focus but triggers other processes(actions).

 

When using this action, consider the target device and its SIP (Virtual Keyboard). In the case of Windows Mobile devices, if the target device uses a custom SIP instead of the OS default SIP, it may return an unexpected system key. This means the "Hotkey" action will NOT be triggered and the associated processes will NOT be executed.

 

In the case of Android devices, due to its OS implementation that manages data input (ex: the SIP), the use of "Hotkey" actions in controls that enable keyboard input (ex: Input Keyboard, Input Barcode, etc.) is NOT recommended. The data entered with the Android device's SIP is considered text and does NOT trigger the "Hotkey" actions you added to the control.

 

Avoid the following combined uses of "Hotkey" actions/softkeys:

•The adding of Softkeys and "Hotkey" actions that refer to the SAME KEY in the same screen.

•The adding of Softkeys and "Hotkey" actions that refer to "<ENTER>" in a screen that contains controls that use "<ENTER>" for their default validation (ex: an Input Keyboard or an Input Barcode).

 

When associated to screens, this action can be used to enable the use of the "swipe" mechanism to navigate the application's screens:

 

1. Add the "Hotkey" action to the intended screen and select the intended key code in the corresponding drop-down:

 

•Key Code "<RIGHT>" - the operator swipes right to left OR  uses the "<Right>" cursor key to navigate to the next screen.

•Key Code "<LEFT>" - the operator swipes left to right OR  uses the "<Left>" cursor key to go back to the previous screen.

 

2. Add a "Go to" Branch process to the "Hotkey" action and refer the name of the intended screen as the target.

 

 

 

7. Power

This action is used to trigger an action the moment the device is connected to an external power source (ex: a cradle). The action (process) will continue to run even if the device is immediately back on battery.

 

8. Validate

This action is only executed if:

a) there are controls on the screen requiring validation and

b) their input is, in fact, validated. This background validation uses all established settings from the "Screen Properties" window.

 

If there are no controls that require validation on the screen, there will be NO input validation and, consequently, the action “Validate” will NOT be triggered.

 

 

By default, this action adds a "Go To: <Routine Out>" Branch process to the screen's "Actions" tab, even if the screen does not include a "routine out".

Consider the following situations/expected behaviors when developing your project:

•Screen was added a "Validate" action containing the default "Go To: <Routine Out>" + screen does NOT include a "routine out".

Expected behavior - the workflow continues to the next screen after all controls have been validated.

•Screen was added a "Validate" action containing the default "Go To: <Routine Out>" + screen includes a "routine out" with processes.

Expected behavior - the workflow continues to the current screen's routine out and its processes are executed after all controls have been validated.

•Screen was added a "Validate" action and the default "Go To: <Routine Out>" was removed + processes were added to the screen's "Validate" action + screen may/may not include a "routine out".

Expected behavior - the workflow executes the processes added to the screen's "Validate" action after all controls have been validated.

 

 

Ensure that the "Execute after all inputs are valid and last Tab Order control loses focus" option is checked.

 

 

Checking this option means the "Validate" action will be triggered by the following conditions:

 

•When all the screen's input controls have valid inputs, meaning, the input values meet the criteria defined for each control (ex: an Input Keyboard control with defined minimum/maximum values or an Input Barcode with a defined pattern)

 

AND

 

•When the control that is set as last in the screen's "Tab Order" loses its focus (if the controls have an enabled "Tab Stop" option).

 

 

9. Receive Message

This action is triggered whenever a message is received by the mobile device (through the Messagebox Service). The mobile device is continuously listening for new messages, so this action can occur multiple times within the same screen.

When a "Receive Message" action is added to a screen, you must define the related settings in its properties window:

 

 

a. Select the intended topic profile in the "Topic Name" drop-down OR  click to access a table with a list of the available topic profiles and select one. If required, you can also edit an existing topic profile or create more. See To Create a Messagebox Topic Profile.

 

This action uses predefined local variables to store the message information:

 

 

10. Custom Actions

If necessary, you can define customized actions to retrieve specific data and notify the intended program - each custom action has its own parameters. These actions are defined at project level to be used in screens, throughout the project. See Custom Actions.

Once defined, the custom action becomes available in the action's properties window. Scroll down the action list to get to the "Custom Actions" section OR  click to access a table with the available custom actions, in case you want to edit one or create more.

 

 

 

To add an action to a screen, use one of the following:

 

•right-click the intended screen (which is open in the "Working Area"), click "Add Action" in the resulting menu and select the intended action from the drop-down and define its settings in the action window.

 

•Open the intended screen's "Actions" tab, click (located on the bottom left of the "Actions" tab) to open the action window and, then, select the intended action from the drop-down and define its properties.

 

•right-click the intended screen's representation in the tree view, click "Add Action" in the resulting menu and select the required action/define its settings in the action window.

 

Each screen can contain as many actions as necessary.

Once a compatible action is added to the selected screen, you will be able to add the necessary processes to it.

 

To add processes to an action, use one of the following in the screen's "Actions" tab:

•Double-click an empty line (under the intended action) to open a "Process List" window (see Detail of Process List) and select the appropriate process.

•Select the required process group in the "Process" tab (located to the right), drag the intended process from the "Process Display Section" below and drop it under the intended action.

•Click (in the editing bar) to open a "Process List" and select a process.

•Right-click an empty line under the intended action, click the "Add/Insert" option and, in the resulting "Process List", select the intended process.

 

To edit the properties of an action or process, double-click the intended element to open the corresponding properties window and make the required changes.

 

 

The Screen's Right-Click Menu

 

As mentioned earlier (see Setting of Screen Properties), the screen's properties window can be accessed by right-clicking a screen's empty space and selecting "Edit".

This right-click menu includes the following options:

 

 

 

 

Tab Order

 

The tab order defines the order that Input controls and/or Menu/Selection controls will follow when pressing the "Tab" key or when the control is validated within a screen.

To have a control follow a defined tab order, it must have the option "Tab Stop" enabled (in the control's "Layout" tab).

To view the screen's tab order and/or change it, proceed as follows:

 

Step-by-step

 

1. Right-click an empty area of the current screen.

 

 

Remember that this option is only available for screens that contain more than one Input or Menu/Selection controls with the "Tab Stop" feature enabled.

 

 

2. Select the "Change Tab Order" option.

 

 

The Input controls come into focus displaying an overlapping red square with a number that refers to the current tab order.

By default, the tab order is set according to the control's position within the screen - from top to bottom and from left to right.

 

3. If required, change the tab order by clicking each control in the intended sequence, meaning, your clicking sequence will become the new tab order:

 

 

Ex: In this example, the "New Tab Order" (2.) was the result of the following clicking sequence executed in the "Original Tab Order" (1):

1. The Keyboard control was clicked (the corresponding number turned into a "1");

2. The Barcode control was clicked (the existing number was replaced with a "2");

3. The Input List control was clicked (turning its number into a "3");

4. The File Browse control was clicked (the corresponding number changed to "4").

 

4. Press <ENTER> in your PC keyboard to apply your changes.

 

As an alternative to step 4, you can use the screen's right-click menu:

 

a. Right-click an empty area in the screen.

 

b. In the resulting menu, click "Change Tab Order".

 

 

c. Click to apply your changes, to set the focus back on the screen without applying your edition or to keep focus on the input controls and be able to modify the tab order.

 

 

As an alternative, use the Drag-and-Drop of the intended Input/Menu Selection controls within the tree view - the first control to be represented in the tree view is the first control to receive input, then, the next control and so on.

 

Example of Tab Order Change via the Drag-and-Drop of the Controls in the Tree View

 

 

 

Detail of a "View All Actions" window

 

 

The "View Actions" window is used to view all the elements included in the active screen (actions, controls, processes).

It is editable, meaning, you can add actions/processes to either screen or existing controls as well as edit their properties.

 

Possible Operations:

 

•Add actions to the current screen or an existing control:

▪via a double-click

▪via a right-click menu

(For information on the compatible actions for screens and/or controls, see Actions associated to Screens and/or Actions associated to Controls.)

 

•Add processes to an action:

▪via the right-click menus,

▪by dragging the intended process from the "Process" tab,

▪through the button in the editing bar.

 

•Open the properties window of the current screen, an existing action/process/control for viewing/edition purposes:

▪by double-clicking the intended element.

 

•Modify process execution order:

▪by dragging the selected process to the intended target,

▪using the (cut), (copy) and (paste) icons from the editing bar.

(For information on the compatible actions for screens and/or controls, see Detail of a Process List.)

 

 

Available Right-Click Menus

 

Below are all the available right-click menus in the "View All Actions" window.

You can right-click a representation of a screen, an action, a process and/or a control.