MobiFlight / MobiFlight-Connector

MobiFlight is an open source project that allows you to create your own home cockpit for your favorite flight simulator in a flexible, affordable and extremely user-friendly way.
https://mobiflight.com
MIT License
235 stars 104 forks source link

Add option to link/embed config sets instead of merging only #1826

Closed joeherwig closed 1 month ago

joeherwig commented 1 month ago

Is your feature request related to a problem? Please describe. I'd like to maintain a standard set for my Joystick axis, Thrust levers etc. that can be referenced to (aka linked/embedded) into other more specific profiles to avoid that I need to go through all my profiles to update the standard axis, when I change something on them.

Describe the solution you'd like It would be brilliant, if there where an option to include mcc files into aircraft profiles. It could be used for instance to maintain a MiniFCU config, a HOTAS Warthog config, a Throttle-Unit config adressing for instance the Asobo generic variables for aileron, rudder, elevator, Throttle-Lever Pos:index etc. That would offer the option to prepare sets, that can be easily stacked together in case of a new Aircraft I wanna setup. It would be perfect, if there would be an visible guidance what "belongs together" like FCU, MCDU, Throttles, Glareshield, Overhead-Lights etc. (kinda grouping, Treeview etc.)

Describe alternatives you've considered Currently I'll make the change in one aircraft test it, save it as new standard file for imports, and delete all the unwanted parts. Then I open the next aircraft search for the affected lines, delete them and merge the updated one. That way I proceed with all the aircraft I wanna update. That's quite time consuming.

Additional context It is brilliant to have the "merge" option already and that it contains already all the variables, etc. Thanks for that!

DocMoebiuz commented 1 month ago

Thanks for submitting this idea! This will be implemented in the new UI.

There is an issue available that covers this scope: #1691

I will close this issue as "duplicate"