Thanks - d_stanz:
Rewrote the code as per your suggestion (much better) and although it made no difference to the operation of the animation your suggestion set me on the path to finding the issue. I then switched to debugging in visual studio code on windows (deploying to the pi later) rather than directly on the Raspberry pi. This showed that the animation was running in a separate thread second time around -- as result of using apscheduler and pydispatch to manage the timed image change. Worked perfectly when I got it running on the main thread. The apscheduler and pydispatch mechanism was carried over from a previous development of message Queue based sensor stations that don't have GUI components. Will now remove pydispatch and use signals /slots.
Thanks again
Bookmarks