Clicking an unset 3 state checkbox should default to enable, not disable

[BretJohnson]

This issue applies to both bool properties and combinable properties that support unset and thus show 3 state checkboxes.

In both cases, when a checkbox is in the unset state and the user first clicks on it, it moves to the false / unchecked state. It probably should go the true / checked state instead, on first click, as that's what the user would likely expect. It's what Android Studio does as well.

[BretJohnson]

@cobey or @JonDouglas can you confirm this is the UX we want.

[ermau]

This starts at -1000 for me, it's not the default behavior for Windows or by extension VS for tri-state bools in an indeterminate state.

It probably should go the true / checked state instead, on first click, as that's what the user would likely expect.

This isn't based on anything other than "that's what Android Studio does". Given it is not the normal behavior for this element elsewhere in the host platform, I'd argue that it's more likely to be the opposite of what the user would expect.

It's what Android Studio does as well.

Matching Android Studio has never been and is not a goal. We live in VS. This argument is irrelevant to any other target platforms we support.

[BretJohnson]

Tree control tristates behave this way in VS. Can you give an example of others? I looked but didn't see any.

[ermau]

What is "tree control tristates" ?

Can you give an example of others? I looked but didn't see any.

The checkbox for the actual value we're discussing in the first place:

Also just checkboxes in WPF by default.

[BretJohnson]

By "tree control tristates" I meant the Exceptions Settings dialog, for instance.
And by examples in VS I meant, of course, outside of Proppy itself.

[ermau]

And by examples in VS I meant, of course, outside of Proppy itself.

That's from the WPF designer for the Checkbox control.

[BretJohnson]

Ah, interesting. When does the WPF designer show 3 states like that? I tried but didn't see that.