mmmm... it appears that I was mistaken. Both trackball movement and screen taps generate MotionEvents. They are delivered completely differently, though Trackball events through dispatchTrackballEvent, and touch events through dispatchTouchEvent.
I remain mystified by how the trackball is handled. It begins to look as if it generates MotionEvents exactly as the touch screen does. Presumably, clicking it generates a KEYCODE_DPAD_CENTER event. How do you generate a KEYCODE_DPAD_UP on, e.g., a G1? -blake On Jan 10, 4:40 pm, blake <blake.me...@gmail.com> wrote: > I notice that TrackballEvents are different that MotionEvents, and it > makes me wonder what happens on a device that does not support a touch > screen. > > Suppose I have an Etch-a-Sketch application, that allows me to do > crude drawings on my screen. With the G1 phone, I just watch for > MotionEvents and draw them. > > Can anyone confirm (or deny) that, on a device that doesn't have a > touch screen, my application will not work? Or, possibly, might > trackball events appear as MotionEvents, on such a device. > > -blake --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
