You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Merge does not change the GUID of inputs and outputs on the merged file. This makes it impossible to import a file more than once. This function can be useful to import, for example, those panels that aircraft have more than one, like radios or MCDU.
Describe the solution you'd like
New checkbox in the merge function dialog to optionally regenerate all GUIDs. When checked, MF will create new GUIDs for every input and output config before importing it into the existing profile.
Describe alternatives you've considered
Alternative is to manually edit the GUIDs which is impractical and error prone.
Additional context
None
The text was updated successfully, but these errors were encountered:
I would just do this every time the file merges. Users have no idea what GUIDs are and shouldn't have to care. The checkbox won't mean anything to them.
This might be tricky to do since it would have to handle updating config references.
Is your feature request related to a problem? Please describe.
Merge does not change the GUID of inputs and outputs on the merged file. This makes it impossible to import a file more than once. This function can be useful to import, for example, those panels that aircraft have more than one, like radios or MCDU.
Describe the solution you'd like
New checkbox in the merge function dialog to optionally regenerate all GUIDs. When checked, MF will create new GUIDs for every input and output config before importing it into the existing profile.
Describe alternatives you've considered
Alternative is to manually edit the GUIDs which is impractical and error prone.
Additional context
None
The text was updated successfully, but these errors were encountered: