[itsme]

Hello Mike,
Thanks for the clarification. I was confused by the "set starting key" dialog looking so similar to the transpose dialog that I wondered about disappearing buttons.
But I disagree in several points:
- the "Detect Key By" setting is not working. If I newly import a ChordPro file and open the transpose dialog it always shows "C/Am". Only the {key: tag is used to detect a starting key during import, not First Chord / Last Chord / Chord Progression.
- the same issue exists with automatically filling the "Keys:" field of the song editor during import: only the content of {key: is copied, not the result of "Detect Key By"
- a starting key can be automatically detected from the content of every ChordPro file: if {key: exists, that's it, it overwrites First / Last Chord. If no {key: exists you can look at the chords in the file and follow "Detect Key By". If there is no chord at all in the file, the whole transpose dialog is useless and should do nothing, it is not relevant anyway
- if "starting key" once is wrong, due to the issue mentioned above or because I erroneously touched the button "Set Starting Key", "Reset" does NOT what I expect. The only way to get back  is opening the file in a text editor outside MSP, look at the contents, then return to MSP and correct the starting key - a tedious procedure
IMHO the previous UI with three buttons "Original Key", "b" and "#" was perfect and clear, no need for another button.
Another little issue:
The "#" and "b" buttons are not working when the original key is C/Am. But they should work: even if the key is C, there might be chords in a song where it matters if they are shown with flats or sharps, e.g. "Night And Day" in C starts with an AbMaj7 chord