It is seriously easier for them to chord ALT+TAB (both on the left side of the keyboard making it especially awkward) than to move the trackball? Well whatever.
But anyway, your code will break on pretty much any other future device than the G1 -- those that have a different keyboard layout, and those that have a soft keyboard (and in the future on a G1 when the user is typing with a soft keyboard). And it could break in rather severe ways, if a device happens to have ALT+Q mapped to something else. At the very least you should go through the keymap to correctly determine if what they are pressing is actually a TAB on their keyboard. On Thu, Dec 18, 2008 at 4:15 PM, Keith Wiley <kbwi...@gmail.com> wrote: > > Well, I understand your point, but I'm writing a program in which the > user might be doing lots of data entry into numerous text fields. In > my own testing so far it is much much easier, less error prone, and > generally more efficient to do this with the tab and return keys > instead of the thumb wheel. Permitting tab and return key events to > jump focus makes a lot of sense. If the API doesn't officially > support it, that's okay, but I'm still going to provide it in my app. > It's just too useful a functionality to dismiss. > > Thanks though, I'll be sure to keep a close eye on how this user > interaction is handled on different devices as Android branches out. > I'm probably programming myself into corner on this one. > > I suppose I could not do it at the keyboard level, but rather detect > the introduction of a tab character into the edit text, remove it, and > then jump the focus at that time...just brain storming. > > On Dec 17, 4:35 pm, "Dianne Hackborn" <hack...@android.com> wrote: > > On Wed, Dec 17, 2008 at 9:37 AM, Keith Wiley <kbwi...@gmail.com> wrote: > > > Nevertheless, I am actually trying to implement a rather common UI > > > mantra, where tab jumps to the next edit text (focus right or down or > > > something logical like that). > > > > That is only common on desktop UIs. On phones, the user typically > navigates > > with a DPAD or trackball or scroll wheel. If we ever decide to support > > desktop keyboards as a formal input mechanism in the UI, the platform > will > > take care of mapping tab or whatever to focus changes just like it does > for > > DPAD and trackball events. > > > > -- > > Dianne Hackborn > > Android framework engineer > > hack...@android.com > > > > Note: please don't send private questions to me, as I don't have time to > > provide private support. All such questions should be posted on public > > forums, where I and others can see and answer them. > > > -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support. All such questions should be posted on public forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
