I have just discovered that wx will sometimes stop generating idle

events (if user stops moving the mouse), meaning that idle tasks can get
stuck in the idle queue, and not processed until the next UI
event. Therefore, the idle loop now gets periodically called by a
wx.Timer, in addition to via EVT_IDLE events.