A UI improvement for "Swing Settings" and "Capo Settings"
Reported version
3.4
Type
Ergonomical (UX)
Frequency
Once
Severity
S5 - Suggestion
Reproducibility
Always
Status
active
Regression
No
Workaround
No
Project
In System/Staff Text Properties, there is a "Swing Settings" tab. Suggestion is to remove the existing "Swing Settings" checkbox and add a radio button instead, as shown below:
Default setting for System Text.
Comments
See #301249: A UI improvement for "Capo Settings", including my half-hearted reservation. I think if we had a dozen tabs here, a simple checkbox for each for consistency - or some other consistent interface - would make sense. With just these two, maybe it's not a big deal. Still, definitely worth thinking about the overall design here.
Typo.
(See Grammar.com: "A" vs. "An" - When to Use)
The suggestion for Capo Settings is the same, see #301249: A UI improvement for "Capo Settings".
The suggestions are connected but not the same. Both involve removing the tickbox and substituting a radio button. But since they are different dialogues with different functions, and since "Capo settings" also requires a small additional reconfiguration, IMV, they should be separate issues.
Sorry, I don't see any difference. Suggestions for different dialogues, but technically the same. And if somebody is going to implement this, there's no reason to do these two separately.
To me the advantage of tying the issues together is to make sure they the changes are designed and implemented consistently. I would not recommend changing one tab without a corresponding change to the other. Of course, a complete redesign of the whole dialog is perhaps worth considering too. I don't think anyone particularly likes how the channel tab works, either. It's really the same issue - differentiating "do nothing" from "explicitly set to default channel". And then there is the MIDI Actions tab, which I cannot prove does anything at all.
In reply to To me the advantage of tying… by Marc Sabatella
The MIDI Actions tab doesn't do anything, just like the Articulation Properties dialogue. For the latter, core codes were all commented out.