Curiosity: radio buttons vs checkboxes #8167
Replies: 1 comment 3 replies
-
One complication is that I consider radiobuttons overrated things primarily understood by designers and programmers so I never bothered writing any at first. Cf. https://uxmovement.com/forms/why-radio-buttons-and-checkboxes-cant-co-exist/. Besides which, the font menu was literally about the only place where it would've been useful at the time, and it was already using checkmarks going back years more. You'll note there was about a year in between when I wrote the two. I'm not convinced that clarity would be helped by replacing the font menu with radio buttons, but feel free to switch it. Looks a little something like this (but you'd have to do a bit more than just swapping out checkmark for radiobutton like I did to make this screenshot). |
Beta Was this translation helpful? Give feedback.
-
This is just a question out of my curiosity. In KOReader, why checkboxes are used in places where radio buttons are expected / more appropriate? I mean the aesthetics.
AFAIK, in general, radio buttons are for items that are mutually exclusive, thus you can select only one item out of the list. Checkboxes are for lists where multiples items can be selected.
For example, in choosing Fonts, there is only one font that can be chosen at once. Or in Highlight drawing style (Underline, Lighten, Invert). Or in many other places (Stable vs Development update channel, etc).
Radio buttons are only used in keyboard layout dialog and selecting render engine for a book, CRengine vs MuPDF, (or maybe in some other places I don’t know yet like plugins I don’t use).
Is it related to some legacy complications?
Beta Was this translation helpful? Give feedback.
All reactions