Focusable in touch mode should not be used outside of the framework. It is meant for very specific widgets that know how to handle this case.
On Sun, Apr 13, 2008 at 10:04 AM, Ted Hopp <[EMAIL PROTECTED]> wrote: > > A couple of follow-up details. Turning off focusable in touch mode > (while undesirable for my app) fixes the scrolling problem...mostly. > Now, when I scroll in touch mode to a position where no focusable view > is visible it stays there. So far so good. However, if I now switch to > keypad mode by pressing the UP key, focus transfers (and scrolling > jumps) to the first focusable BELOW the current position, and if I > press the DOWN key, focus transfers to the first focusable above. This > seems completely backwards to me. > > > > > > -- Romain Guy www.curious-creature.org --~--~---------~--~----~------------~-------~--~----~ 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] Announcing the new M5 SDK! http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
