Default MIDI settings not applied where there is a default .cmb file

[ahall41]

Where there is a default combination file, containing (say) combination or tuning settings only, which is then loaded on startup, the default MIDI settings (keyboard, swell, GC, etc), should also be applied.

[ahall41]

A few more "oddities" where there is a default .cmb

• Unless (I assume) the organ is installed in exactly the same folder as when the .cmb is created, you get a message 'The .cmb file does not exactly match ...'
• Reset to Defaults is enabled, but if you use it, you get an error deleting the .cmb which you haven't (yet) saved.

[ahall41]

Some suggestions:

1. As well as importing a default .cmb settings, also import a default .yaml with the same name as the .organ
2. If the .cmb file does no contain a midi (or key stroke) setting, apply the default after import (including import settings)
3. OR Apply defaults after importing a default cmb (but not after a saved .cmb)
   I think it can be assumed that, by and large, the defaults are what the user wants to use?

[oleg68]

1. As well as importing a default .cmb settings, also import a default .yaml with the same name as the .organ

There is no any reason of importing a default .yaml because the combinations can be stored in the default .cmb.