New Search Dependent Output Configs

[JaimeLeon2]

Is your feature request related to a problem? Please describe. With increasingly complex configs that use a lot of interconnected output configs it becomes very difficult to remember what is connected to what. A "Search for Dependent Configs" function would greatly help track and identify which configs (input or output) are currently using a particular output config as reference.

Describe the solution you'd like A new "Dependent Configs" dialog window where the user selects an output config from a dropdown menu with the existing list of all output configs (alphabetically sorted, please). Once an output is selected the app lists all the input and output configs currently using the selected output config as a reference or in preconditions. Clicking on one item in the search results list automatically opens that config wizard for review. Closing the wizard returns to the search results list. Options in the search dialog should be "New Search" (activates the list dropdown) and "Ok" (exits back to main screen).

Describe alternatives you've considered Currently there is nothing but our own memory to do this.

Additional context nothing

[DocMoebiuz]

Ok. So at the moment we have the other direction, like I can see which config references I am using in the current config. But you cannot see by what other configs the current one is referenced.

In what circumstance do you need this "navigation" feature?

We could introduce an additional tab (after preconditions) with something like that, or create a config reference tab where you can:

• define the config references that you would like to import
• see the configs that are referencing the current config

I would still like to know why you would want to go to dependent configs. I think I can see immediate benefit in navigating to a config reference that you are including as placeholder in your current config.

[JaimeLeon2]

I find it difficult to remember if and where every output config is used. Can it be safely deleted? Is it used anywhere else? Why is this config here? Currently, as you pointed out, the relation is one way. The user can only see which output configs are used in one particular config. To answer where is an output config used the user would have to open and review ALL input and output configs.

[DocMoebiuz]

I think deleting is a good point. A message telling you: "this config is referenced in 2 other configs, do you really want to delete it?"

that would be helpful.

[JaimeLeon2]

If Mobiflight can tell you that there are two configs using this config, then it should be easy to also list which ones are they, no? User may want to edit those before deleting the config. This can be also useful when converting one mcc from one airplane to another.
I never start a new mcc config for a new airplane from scratch. All the devices in my panel are already defined in input and output configurations of other airplanes, it is just a matter of selecting the appropriate events for the new airplane and the panel logic may be different, so tracing dependent configs help to navigate faster.