I'm suggest we be just a bit more explicit in explaining the validation design: and say clearly that every button selection must result in a valid combination.
This might seem too obvious or sufficiently implied.. I know. Don't people use enough UIs that they'd know this? Possibly.
Along with that I made the notes/examples a bit more explicit as far as what actions to take, which turn the statements of support into more implied statements rather than explicit ones. (That's a mouthful..just look at the text :) )
I'm suggest we be just a bit more explicit in explaining the validation design: and say clearly that every button selection must result in a valid combination.
This might seem too obvious or sufficiently implied.. I know. Don't people use enough UIs that they'd know this? Possibly.
Along with that I made the notes/examples a bit more explicit as far as what actions to take, which turn the statements of support into more implied statements rather than explicit ones. (That's a mouthful..just look at the text :) )