[itsme]

The sharp/flat buttons on the transpose dialog seem to switch only the enharmonic equivalent of the destination key. I would expect that it also affects how chords are displayed within the song.

There's a really ugly work-around: if I set a wrong starting key in a way that the (also wrong) destination key has an enharmonic equivalent, then I can tweak that the song is displayed as I want it.

See attached example. If I transpose "What A Wonderful World" (with chords in F within the file) I would like the Db in the 5th measure of the A section to be transposed to Ab, not G#.

If no transposing is set (starting key = destination key) the chords should be displayed unchanged, as written in the file, to allow the rare case of mixed sharps and flats in one song

I'm not sure if that worked as expected before the implementation of the chord localization feature.
I tested with MSP 2.7.3 on Android.