Does a tag assigned to a section apply to all items in that section?
Is there a way to find / edit all uses of tag?
Is there a way to globally edit a tag? For example if the tag was FUBAR and I wanted to change it to Departure FUBAR.
A tag assigned to a Section or List applies to the entire Section or List. Meaning if you add a tag to a Section or List it will either hide or show that entire Section or List. There is currently no way to find / edit all uses of a tag. It is something we will add to the backlog.
Another suggestion for tags would be for them to have multiple choices, or at least two. There are a number of procedures that are either A or B. For example:
Towered or non-towered
VFR or IFR
Hangar or Tiedown
The tags/filters are a powerful tool to adapt Mira to different operations.
An interesting suggestion. I will need to think through it a bit. Seems like tagging would be done the same way where you would tag things IFR, VFR, etc. And then a configuration screen where you would tie the tags together. So for example if IFR and VFR are tied together, then the UI would present a selection of radio buttons with VFR and IFR as options so you could select one. This could work with one-to-many as well like Landing Airport Class A, Class B, Class C or Class D.
Yes. The “configuration” screen you illude to would enable tieing tags together, probably in ways that have not yet been anticipated. Alternatively, to simplify implementation, the configuration could be a special List (perhaps special in name only) at the top of the Checklist where tags could be grouped within Sections enabling a tag to be in multiple groups. With the same editing UI, you would add a “tag” item that could be added to a “tag group” (aka Section) using all the same editing constructs you have today. A tag could then appear in multiple groups or in the simplest case the tag group would contain only one tag.
Then when today’s Filter UI is presented when a Checklist is reset, the user would select which “tag groups” to enable. It could most be done with almost no UI changes, and only minor changes to internal logic as downstream the logic would be looking at the same tag state flags you are presumably using today.
I’ve been using tags/filters quite a bit as a result when I start my checklist I have to go through about 15 filter switches. Is there a way to set a filter as an action from a picker list? It would be nice to defer some of the filter settings until later in a flight/landing and a picker list would be a convenient to defer the selection until later.
This would not necessarily be 1:1. I might select choice “X” from the picker list and then set filters A1, B3 and C4. This would solve the issue I raised last year and basically push the programming off to me rather than you.
The filters are something that run one time when a procedure is launched to filter it down. To allow it to dynamically be changed once in the checklist not as trivial.
So I guess we’ve reached the end of the evolution of tags/filters. They are what they are. Too bad because flying is nothing if not about addressing to a dynamic environment.
I think I said it was not trivial. We have by far the most dynamic capabilities of any procedure system and continually look at areas for improvement. We have rolled out new capability which will give you complete control of doing advanced requirements as you are requesting, and yes, put the programming on you. You will notice in the MiraCheck Cloud app some new properties such as Visible, Group Names and Value Triggers. These can be used to do very advanced things at runtime and should meet your dynamic environment requirements. We are still working on putting the documentation together, so stay tuned!
Looking forward to it and standing by for the documentation.