> > So, please, when you ask questions, also try to explain WHY!!!! > > In his second post the OP said: > > > I'm experimenting with different behaviors. > > Seems to me that's reason enough.
And I am defending my first reply. On Sep 17, 10:21 pm, DanH <[email protected]> wrote: > > So, please, when you ask questions, also try to explain WHY!!!! > > In his second post the OP said: > > > I'm experimenting with different behaviors. > > Seems to me that's reason enough. > > On Sep 17, 12:13 pm, Kumar Bibek <[email protected]> wrote: > > > @DanH: Agreed. But the situation you put forth, to achieve that, you > > probably should not be altering the ListView's scrolling direction. If > > you can explain your requirements correctly, you would ofcourse be > > getting answers on that context. > > > If you would just ask, How to run an .apk on a Blackberry, you would > > obviously get such replies. But, if you say, I have loaded my > > Blackberry somehow, with the Android OS, and now I would like to know > > how to run my apps on that device, you will get different answers. > > > So, please, when you ask questions, also try to explain WHY!!!! which > > would help others understand your problem, and give solutions > > accordingly. > > > -Kumar Bibekhttp://techdroid.kbeanie.com > > > On Sep 17, 10:04 pm, DanH <[email protected]> wrote: > > > > 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
