FYI, the problem isn't that the Swing timer is on the "wrong" thread - it is that the Pivot runtime needs to handle the callback so that the layout system can be invoked properly. In most cases, you are probably going to do something in your callback that will invalidate your UI and trigger a relayout. Using the ApplicationContext methods as Chris suggested ensures that this will happen, whereas using the Swing timer it won't.
On Jan 18, 2011, at 7:46 PM, Bill van Melle wrote: > Is there a sanctioned timer class to use that fires in the UI thread? I > tried using javax.swing.Timer, which sort of works (in that it doesn't > complain about being on the wrong thread), but actions taken by the timer > callback don't manifest in the UI until the next time something runs code in > the UI thread (in my case, a GetQuery).
