We’re all very happy to have CygNet 9.4 out in the world. The CygNet development and product management team worked hard to ensure this release would provide significant value for our customers. Hopefully you can see the results of that work in the massive 9.4 release notes.
As the lead developer for Canvas, I want to spend some time highlighting some of the many new HMI features in 9.4. This release represents the biggest investment we’ve done in our new HMI since it came out a few years ago. Frankly there are just too many new features to meaningfully cover in a single post, so I am going to break it up and do a series on some of the awesome new things in Canvas.
Today I want to talk about navigation. Navigation is a big theme for Canvas 9.4. As people start building out new systems in Canvas, we wanted to expand options for end users to move around quickly and efficiently.
Relative facilities have been around in CygNet in some shape or form for many years. And along the way, there were enhancements made to Studio to assist in creating multi-facility templated screens based on a relative linking model. However, with Canvas, that relative linking functionality and resolution was baked into the product at the very beginning. In this post, I’m going to discuss some design considerations and implementation ideas that I hope will help as you create Canvas screens.
Well as a similar joke goes, first the tab strip has to want to change.
Tabs are commonly used in screen navigation. They do a good job of helping us organize our screens and they don’t require a lot of screen real estate. I used them extensively when building CygNet for Production. So much so that Applied Engineering built an entire management system to control the configuration of the tabs, but that’s a story for another day.