12-16-2015, 02:07 PM
If having faster access to the transpose feature is critical, I can certainly add a new button that handles just that. I can also look into a faster UI for selecting the target key (whether by selecting a key or steps).
Johan, I'm starting to forget all the history, but I remember there being issues with transposing that were only handled if I considered the key of the song when choosing what chords to use (flat versus sharp). If you believe that following the simpler approach of "transpose up = sharps, transpose down = flats" handles all scenarios, then I'm fine with switching to that. Whether the transpose slider displays steps or the target key (based on the original key of the song), I don't think it matters so long as I'm consistent with how the transformations happen in the code (i.e. only by considering steps up or down).
Thanks for all of the feedback and advice.
Mike
Johan, I'm starting to forget all the history, but I remember there being issues with transposing that were only handled if I considered the key of the song when choosing what chords to use (flat versus sharp). If you believe that following the simpler approach of "transpose up = sharps, transpose down = flats" handles all scenarios, then I'm fine with switching to that. Whether the transpose slider displays steps or the target key (based on the original key of the song), I don't think it matters so long as I'm consistent with how the transformations happen in the code (i.e. only by considering steps up or down).
Thanks for all of the feedback and advice.
Mike