Instead of wx.FutureCall please use wx.CallLater.:::0:9f85c54189f53f90605a17bc9b054146:-1:x:::
OK. Have just tried wx.CallLater… am still getting the same error message.
···
On Sunday, 2 June 2013 14:16:01 UTC+8, Boštjan Mejak wrote:
Instead of wx.FutureCall please use wx.CallLater.:::0:9f85c54189f53f90605a17bc9b054146:-1:x:::
Bo�tjan Mejak wrote:
Instead of wx.FutureCall please use wx.CallLater.:::0:9f85c54189f53f90605a17bc9b054146:-1:x:::
wx.FutureCall and wx.CallLater are the same thing (one is an alias) so for the purposes of this discussion switching from one to the other makes no difference.
···
--
Robin Dunn
Software Craftsman
Using wx.CallLater is future-proof.
Bo�tjan Mejak wrote:
Using wx.CallLater is future-proof.
Yes, but writing about it as if it was a solution to his problem only adds confusion.
···
--
Robin Dunn
Software Craftsman