There's nothing to fix; that is what is supposed to happen. Even if it WERE called immediately -- you'd not see any updates to the view until onTouchEvent() exits.
You'll need to allow the rest of the system to run between steps of your animation. I'm not sure what to suggest for your tile consolidation, because I'm not sure of the intended behavior. You may want to repeatedly post a Runnable so long as there's still consolidation to be done, or you may want to run it on a timed basis. On Apr 16, 7:38 am, Dave Fine <[email protected]> wrote: > My project has a View that is supposed to start its tween animation > (using startAnimation()) when onTouchEvent() is called. I would expect > the animation to start immediately since that is what is documented > (http://developer.android.com/reference/android/view/ > View.html#setAnimation%28android.view.animation.Animation%29). > However, stepping through my code, I see it does not start until some > time after onTouchEvent() has finished :-o! > > Does anyone know why this is, and how to fix it? > > My code is available > here:http://github.com/finerrecliner/Finer-Collapse/tree/master/src/com/fi.... > The GameView has the onTouchEvent() which calls consolidateTiles(), > which calls `animate()` in the AnimateView. > > -- > 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 > athttp://groups.google.com/group/android-developers?hl=en -- 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
