On a different phone we ran into this. 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.
I think some folks need to come down off their high horses and accept that ultimately one should do what works, vs what is "right" by the book. On Sep 17, 11:37 am, TreKing <[email protected]> wrote: > On Fri, Sep 17, 2010 at 10:40 AM, Moto <[email protected]> wrote: > > Its none of your business how I would like to use this feature. > > If you come to this group asking for suggestions on how to do somethings > that is literally backwards, it does behoove you to explain the motivation. > There are many, many posts on here where people ask "how do I do X" and when > the motivation is explained, it turns out they should be doing "Y". > Understandably, trying to reverse the logic of a standard control reeks of > this type of post. > > > it will not end up being used were users would expect a listview to behave > > like a list view! :) > > Then why use a list view? > > > I just need tips on how to achieve this... > > OK. Either try extending ListView and overriding the appropriate methods (if > it's possible, not sure), or grab the ListView source, find where it > responds to user input and does the scrolling, then reverse it. > > ------------------------------------------------------------------------------------------------- > 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
