choosers should (probably) accept any value when set from code

Esther (a long time ago):

hey - do we want choosers to accept values that are not part of the choices when set from code? before when I was reviewing stuff I only checked for things that changed values silently. this throws an error but I was thinking maybe that wasn't right

me:

hmm. yeah, I think they should accept any value when set from code. of course then we need to figure out what to display in that case

the argument is that sliders now accept any (numeric) value when set from the code, so choosers should too (without the numeric constraints, since choosers aren't constrained by type). the idea is that the min/max/step values determine what user interface is presented, but it ought to be possible to override that from code.

for example a chooser might present "1, 10, 100, 1000" as choices, but 10000 ought to work if you do it from code, e.g. in the command center.

Search the chooser implementation and the slider handling to compare how values set from code are validated. Reproduce the command-center example with a value outside the displayed choices, then determine how that value should appear in the chooser. Done means code-set values are accepted without the chooser's choice constraints and their display behavior is defined.