In this particular context there was a simulated scroll wheel superimposed over the edge of the scroll list (for reasons having to do with the dynamics of the controls). For some reason this changed the user's perception of the control completely. Basically, the user saw the wheel as moving the highlight bar up/down vs moving the list up/down. (If you think about it, the scroll wheel on a mouse operates the same way.)
I am sure there are other situations where similar perceptual issues could arise, such as when scrolling some sort of a map. And the OP certainly has a right (and perhaps legal obligation) to not disclose the particulars of his application, in addition to simply not wanting to hear even more of "You shouldn't be doing it that way". In programming there are some definite "shoulds" and "shouldn'ts", but in UI design far fewer -- it's basically "whatever works", combined with a modest respect for convention/precedence. On Sep 17, 11:48 am, TreKing <[email protected]> wrote: > On Fri, Sep 17, 2010 at 11:44 AM, DanH <[email protected]> wrote: > > In a particular context "normal" scroll behavior was (almost) universally > > judged by users as "backwards", even though a few screens later the > > situation was reversed. > > What context? If this is clearly explained so the rest of us dumb folk > understand, it would be easier to climb down off the high horses. > > ------------------------------------------------------------------------------------------------- > TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago > transit tracking app for Android-powered devices -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
