> > Why is this not acceptable, and why would this be a flaw?
>
> This is not acceptable because there is _no value_ in tapping on a dropdown
> arrow for a list with only one item that is already being displayed. This
> is a wasted tap, and that is very bad. If there is only one item in the
> list, the user shouldn't be suckered into hitting the dropdown arrow and
> still only seeing that single item. If, instead, there were no little black
> triangle, then the user would go "Oh, I guess this is the only item in the
> list so I'm not going to waste time tapping on it to see if I might be able
> to select something else." Am I jumping off the deep end here, or does this
> seem like a legitimate request?
the control is a list.. hence you display it as one. if there is
one item, ten items, one hundred items.. then it is still a list.
the API is fine the way it is.. if you have one item. you code
it so that it is already selected, OR.. you do the following:
dynamically change the "list" object to a "field" object.
it may be the case where you may say "dont show the arrow" and
what if there is more than one item?? if something can go wrong,
it will.. as murphy states himself.
> contents. This one trigger pretty much drives the whole form, come to think
> of it. Our competitors on this app will eat us up if the end user has to
> make too many taps on any form. One competitor named its company after the
> # of taps it took to complete a transaction, for bragging rights. It's
> brutal, man. After this project, I'll never think about taps the same
> way...
:>
wow.. a new way to look at it.. value of applicatoin = #taps
required :> hehe..
az.
--
Aaron Ardiri
Lecturer http://www.hig.se/~ardiri/
University-College i G�vle mailto:[EMAIL PROTECTED]
SE 801 76 G�vle SWEDEN
Tel: +46 26 64 87 38 Fax: +46 26 64 87 88
Mob: +46 70 656 1143 A/H: +46 26 10 16 11
