You can setup a special menu within the Menubar that allows you to navigate throughout the project using the scripting functions. They can be simple, like swapping to a window, or be more complex in how they navigate around the project. The benefit of using the Menubar for navigation is that it keeps navigation tucked away instead of using up valuable screen space. You can find the screen below in the Client Event Scripts space.
Each of the project templates that you can apply when creating a project uses a unique form of navigation. These are a great resource that can help give ideas on how to tackle navigation, or can be modified to work in your own project. These come in three types:
- Single-tier navigation: There is a single level of buttons, each taking you to a different window
- Double-tier navigation: There are two levels of buttons. The first set controls which set is displayed below, and the second set takes you directly to those windows.
- Multi-tier navigation: There is a single tree-view style display that lists all available windows and can be grouped into folders.
You can select one of the project templates when a new project is created. If you'd like to use them in an existing project, you could just create a new project with the template you want and copy the pages you need to your project.
Local Client Fallback
Local client fallback is not a navigation strategy in the normal sense (you cannot cause it to happen), but it is very useful when you want to ensure a user can continue work when the network goes out. Click the links to learn more about Local Client Fallback and about Ignition Edge.
Testing Local Fallback
Testing local fallback is highly recommended before you start to depend on it in a production setting. The easiest way to test fallback is to simply unplug the network cable to the Client machine, or disable the network card on the machine. If the Fallback Project button is not visible on the Gateway Connection Lost window, check your local Gateway console and verify that the message Started Fallback Socket on port 6501 is present in the console. Any other error message related to the Fallback Socket Controller indicates that some other problem has occurred (most likely the port cannot be reserved) and local fallback is not available to Clients.
Reconnect to Central
In many circumstances, the communication loss to the central Gateway is only a temporary event. To minimize the amount of time that you need to run the local Client, you can add some functionality to the Client that allows you to check on the status of the central Gateway. One way to do this is to add a timer script to your local Client. The script calls the
system.util.getGatewayStatus() function at regular intervals and updates an item such as a Client Tag with the Gateway status. Then, you can bind an indicator component to the Client Tag and get ongoing visual feedback on the central Gateway status. As soon as you can confirm that the central Gateway is running again, you can call the
system.util.retarget() function in a button to seamlessly direct the Client back to the central Gateway.