[Sigia-l] check boxes versus multi-select lists

michel.milano michel_milano at yahoo.com
Fri Jan 14 18:44:42 EST 2005


since you are casting a wide net, then it is worth also considering
what the data wants, independent of what the users want,
as an evaluation axis on its own.

if the list is relatively benign, then a form field select list
might not have any problems.

but if the list is contains critical information whose selection, or 
de-selection, can have serious consequences somewhere in the 
lifecycle of whatever is being worked with?

supposing a workflow or multi-user process involving all engineers,
who themselves insist that the multi-select list form elements take less space
and are preferable to them.
but checkboxes remove that one chance where choice #9, that is 
below-the-fold of the
select-list window, was originally selected but becomes unselected 
because the one
user came mid-flow, and selected the items #2, #3, and #4 but didnt recognize
that they had inadvertently de-selected #9.

the apple font-da mover widget (is there a better name?) mentioned by brett
is intended to address both cases, at the cost of more development 
and support work.

m. milano





At 14:57 -0700 14/01/2005, Taylor, Brett wrote:
>Why couldn't they do another solution, instead of multiple select box or
>check boxes, why couldn't they have two lists, one has all the choices,
>the next is the one that accepts your choices from the first.  Add or
>subtract list? This way it may help people who are handicap or at least
>in the case of the person with one arm and not have to show long list of
>check boxes?



More information about the Sigia-l mailing list