I actually do use the Thread.sleep as a hack (i don't like it, but it works...) It just sleeps for just 20 milli seconds, though. It's enough for a notable improvement in the frame-rate of the other thread (game- thread) and not too big to miss input events. I only do it on the ACTION_MOVE.
On Jun 10, 1:12 pm, MrChaz <[email protected]> wrote: > I've run into an issue where performing a lot of touch events seem to > block the move events from the trackball. > Anyone else run into this issues? > I can't use the Thread.sleep() fix because that will obviously stop > all input, so I'm hoping someone has been able to throttle the touch > command without effecting the move ones. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
