You can help by commenting or suggesting your edit directly into the transcript. We'll review any changes before posting them. All comments are completely anonymous. For any comments that need a reply, consider emailing firstname.lastname@example.org.
We are experiencing playback issues from our video hosting provider. Please check back shortly.
2:49Swapping vs. Opening
2:05Back and Forward Buttons
Take topic challenge
Learn how to use various navigation strategies for your Ignition Vision project.
Video recorded using: Ignition 8.1
Transcript(open in window)
[00:00] In Vision, there are different types of navigation strategies that can be implemented. Despite their differences they all share the same idea. First, you want to pick which windows will open on start-up. Then from those windows you can navigate to any other window or windows you have designed as part of your Vision project. How you navigate to other windows in your project it's up to the navigation strategy that you choose. You can use tabs to navigate around your project. You can use a tree view. You can have a back and forward button, and a lot more. All you are doing is simply opening and closing a set of windows from your Vision client. Let's take a look at some examples. Here you can see your typical navigation strategy on clients startup. I am opening a west docked window along with a main window. The west docked window will remain always open.
[01:03] The currently open main window will vary but there were only ever be one main window open at any given time. I am using tabs from the west docked window to switch which main window is currently open. That is every time I change my selection in these tabs a different main window will be navigated too here on the right. Because I can only have one main window open at once the navigation tabs will close and open main windows as needed. If I needed to I can also use independent buttons to trigger the opening of things like pop-up windows like so. As you can see I am using tabs to navigate around the various main windows in my Vision project. And buttons on this screens to open things like pop-up windows. I can also use tree components to control navigation. Here on this next Vision client I have opened I have a tree component on my west docked window where I can double click on individual notes and navigate to different windows in my application. I can also have back and forward buttons like in this third Vision application.
[02:09] The top buttons on each side basically navigate between different Vision windows. Again, at any given time we are only opening one main screen and we're replacing the currently open screen with a different screen using the swap operation. For many of those windows again, I can also open up pop-up windows like so. The navigation strategy that you choose is dependent on how you want people to navigate within your application. What windows you want open is entirely up to you and your implementation. In future lessons we will explore some of these navigation strategies and take a deeper dive into how they work.