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.