5 ms·
>you should not have double-negative // Hmm, I'd like it if that always made sense, but sometimes the default state, with nothing active, is for Foo to be on.
by pbhjpbhj 4y ago
>you should not have double-negative //
Hmm, I'd like it if that always made sense, but sometimes the default state, with nothing active, is for Foo to be on. So "Disable Foo" is doing something not normally required, or something most people don't want. Sometimes it does make sense that _not_ performing a reduction in Baz is default, and that default is off.
You could probably solve it by renaming a feature to used an antonym, but not everything has an antonym [that people know, or that makes sense].
- ilyt 4y ago> Hmm, I'd like it if that always made sense, but sometimes the default state, with nothing active, is for Foo to be on. Then foo will be checked on by default. That's not a problem. [X] Send notifications Is perfectly unambiguous. What I'd like to see with every option like that is something showing whether it is in default state or not so user can easily glance what was changed from default. "reset to defaults" per page of settings is also appreciated.
- gisborne 4y agoI’m puzzled why you equate “default state” with “nothing active”. If the default should be that thing the button says is on, then have the button default to being in the active state. The language even for discussing this is tiring to read…
- IshKebab 4y agoThe better solution to "is this the default" is to just have some mechanism for indicating whether the value has been changed, and a way to reset it to its default. This is quite common in UIs. It also has the benefit of working for all controls, not just checkboxes.