Keith Wiley wrote: > Consider the following inefficiency > that is imposed by using the trackball: You can't necessarily skip > out of an edit text with the trackball in the desired way because the > cursor may be in the middle of the edit text, in which case > trackballing merely moves the cursor within the edit text.
FWIW, WikiNotes demonstrates that the trackball can be used to navigate from a multi-line EditText to adjacent buttons. I was doing it myself less than an hour ago. > Second, I find myself constantly triggering trackball motions on the > wrong axis. I'm definitely a fan of D-pads, myself. The trackball is excellent for rapid smooth scrolling motion, but it leaves something to be desired for detail work. What could be slick is a combination: D-pad direction buttons with the trackball serving its current role (direction plus "center" D-pad button). It may be the trackball would have to be inset to make that work... > Adjusting one's hands to go > constantly back and forth between the keyboard and the trackball is > difficult unless you physically put the device down on a table. On the other hand, FWIW, I haven't found this to be a problem. -- Mark Murphy (a Commons Guy) http://commonsware.com _The Busy Coder's Guide to Android Development_ Version 1.9 Available! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
