MiraCheck appears to be very linear in its design: Pre-flight » start-up » taxi » takeoff » climb » cruise » descend » approach » land » taxi » park. Done. That’s the way it seems Mira was expected to be used, where someone was going to be going from point A to point B in the most direct fashion.
Unfortunately, I don’t usually go from A to B. I often times go from A to F, come back to C, then B, then E, and maybe back to B again several more times in a row.
For example, what if you’re going to be doing multiple approaches or touch-n-goes for practice?
Or, in another example, a truck driver who stops for fuel several times along his or her coast-to-coast trip. He or she will repeat their tasks to fuel their truck several times before they get from their pickup (“point A”) to their delivery (“point B”), and likely, there are some important steps
when fueling such a large vehicle that make it worth putting them a checklist. And yet, those steps will need to be repeated a few times as he or she makes their way across the country.
I thought about creating separate checklists, but that seems clunky. But it also seems to be the best solution (for this MiraCheck newbie) to a problem I’m having running into linking.
Various lists need to be able to link to “subroutine”-type lists. These are lists the need to be reused throughout the overall life of a checklist (a flight or shipment in the above examples), but then upon their completion, return to the list that called them. But it seems that a “subroutine” list item can only link to one link ID. That means it can only send you back to one predetermined parent list, which may not be the one that sent the user to the child/subroutine list.
What would be the best way to implement these repetitive subroutine lists?