Does this happen every time or only occasionally? Does your code call handler.postDelayed (runnable,miilisecs) in other places or repeatedly? What is the value of miilisecs?
And finally there is a small chance that the runnable will be started just as you call "removeCallbacks" due to threading. On Tuesday, July 3, 2012 12:17:27 PM UTC+1, B.Arunkumar wrote: > > Hi, > > Thank you for your reply. This is roughly the framework of code I > am using: > > Main Thread :- > > Handler handler = new Handler(); > handler.postDelayed (runnable,miilisecs); > > Another Thread :- > > handler.removeCallbacks(runnable) > > But I find that handler.postDelayed (runnable,miilisecs) still > executes after handler.removeCallbacks(runnable) is executed in the > other thread. > > Thank you, > B.Arunkumar > > On Jul 3, 3:49 pm, skink <psk...@gmail.com> wrote: > > B.Arunkumar wrote: > > > Hi, > > > > > Sometimes, handler.removeCallbacks(runnable) does not remove the > > > callback after handler.postDelayed(runnables,millisecs) is executed > > > and the handler.postDelayed again gets executed after some time. Can > > > somebody let me know how to solve this problem? > > > > it just works ok. post your code how you call both methods > > > > pskink -- 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
