Blake is a Principal Engineer in Applied Engineering at Weatherford and has been with the company since 2005 in various capacities. He has almost two decades of experience in designing and integrating CygNet systems. In his current role, Blake works on solutions, tools, APIs, advanced training, consulting, and deployment assistance for the Weatherford service and support teams.
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.
Consider this scenario. I have an overview grid screen that has a list of wells with some high level information. I click on one of the wells and a separate screen opens with more detail. On that detail screen, I click on a button that opens another screen that has a trend with various well points. Cool, I have separate dedicated screens that I’m able to view the various bits of information I desire at the same time. Now I want to be able to select on a different well on the first screen and have the other screens follow. And, I want to be able to look at multiple sets of these screens for different wells at the same time. How can I do that
In my previous post How to change a tab strip selection, I discussed the use of HyperLinkSys as a means of passing data from a nested view screen to its parent screen. In that technique, the data passed from the nested view was used to change the selection of a tab strip on the parent screen. In keeping with the theme of initiating an action from a nested view, I will present a different technique using custom events for more complex interactions.
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.