Transpose should have radio buttons
1. Open score.
2. 'Select All'.
3. 'Transpose...'.
Desired result: 'Transpose by Key' and 'Transpose by Interval' are radio buttons.
Actual result: 'Transpose by Key' and 'Transpose by Interval' are tick boxes.
Using MuseScore 2.0 Nightly Build (74b4a45) - Mac 10.7.4.
Fix version
3.6.0
Comments
I was looking at the Transpose window and mocked up an example of how it could look (there might have to be further refinements - not sure about some things):
You may notice that in addition to substituting tickboxes with radio buttons, I've moved some of the options inward.
I'm wondering, though, if we could relocate the entries in the 'Options' section - namely 'Transpose chord symbols' and the droplist for single and double accidentals.
In the last droplist of 'Transpose', should we remove the words "only" and "use"?
#2: Why ? And how is it related with the main issue?
Regarding the main issue, it's not recommended in UI design to have radio buttons far apart. In my opinion, having radio buttons would be has bad as what we have right now.
The best thing I can come up with for now is a tabbed UI. One tab for "transpose chromatically", one for "transpose diato"/
#2 Yes, I admit tacking it on (I held off, originally). ;)
I'm sure whatever you come up with will be fine.
No activity for over 3 years. It seems nobody is bothered by the checkboxes since I didn't read anything about it in the forum in this time span. I close the issue.
I agree. No need to waste dev time on this.
#304466: The “I/O” tab of the “Preferences” dialog should use radio buttons instead of checkboxes was a very similar issue, and since PR #5992 it presents no difficulty. Anyone actively opposed to changing the appearance of the checkboxes?
The check boxes act like radio buttons. Radio buttons make more sense.
https://github.com/musescore/MuseScore/pull/7037
Fixed in branch 3.x, commit 83a8dcc4d1
_Fix #18038: Change checkboxes to radio buttons for transpose dialog ...
and page style groupboxes_
Automatically closed -- issue fixed for 2 weeks with no activity.