Note: I am not a game developer. David wrote: > 2. What is the best way for us to accomplish trackball events using on > screen buttons? > > 3. How might we disable the hardware trackball?
I would think that the answer to #2 and #3 is: don't consider your on-screen buttons to be a direct replacement for the trackball. So, if you have a typical four-arrow-button on-screen navigation, when the user clicks the "up" button, you have your game do an "up" action. You don't say "oh, well, they clicked the 'up' button, so therefore I want to generate an 'up' trackball event, then route through trackball event processing to do an 'up' action". Once you have adjusted your code to respond only to the on-screen buttons, if this is a 2D game, I would imagine the trackball would have no effect. At worst, you just consume those events, doing nothing. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy Android Online Training: 26-30 April 2010: http://onlc.com -- 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
