Quote:
Originally Posted by Starson17
Here's why I disagree.
|
Seems like we might have irreconcilable differences here.
What do you think about the idea of adding a 'tweak' that controls whether 'no' and 'not-set' are the same thing? Tweaks are intended to be set once, controlling calibre's behavior from that point forward. The more technical amongst us could understand both how to set the tweak and the consequences of setting it, while those who aren't technical or prefer the two-value behavior would leave it alone.
To be precise: if the tweak is set to two-value, the interface will accept only checked and unchecked. Both No and not-set display as No. Editing the value and setting it to unchecked will change the value for the row to from not-set to No, but would have no effect on display. Searching for 'No' or 'false' will find both 'No' and not-set. Searching for 'true' will find only Yes.
If the tweak is set to tri-value: the interface will accept all three values, and they will display differently (No as no and not-set as blank). Searching for Yes (or the alias 'checked') will find only rows with Yes values. Searching for 'No' (or the alias 'unchecked') will find rows with No values. Searching for 'false' (or the aliases 'empty' and 'blank') will find rows with not-set values. Searching for 'true' will find both No and Yes.
Or something like that.
The default would be two-value.
Acceptable?