TimerUtility: allow to specify the thread on which the callback will run

<paulburton> I guess it shouldn't make much difference
 I think I did it because some of the timer callbacks remove their own timer id
 so that would just make sure they got chance to do that before it fires again
<bmotmans> ok
 hmm, now that i think of it, why dispatch at all
 like the NowPlaying utility, it will probably use the timer to poll all
music players
<paulburton> well, most of the code now assumes its on the main thread,
which is why I made TimerUtility dispatch to the main thread
 I know you were worried about performance
<bmotmans> maybe we could add an additional parameter to allow to choose if
the callback runs on the timer thread or the main thread
<paulburton> yeah that would make sense

Original issue reported on code.google.com by ben.motm...@gmail.com on 14 Jun 2008 at 4:40

zD12 / galaxium

TimerUtility: allow to specify the thread on which the callback will run #167