RE: CPU running at 100%, GUI locks up

On Wed, Mar 10, 2021 at 09:46, Steve Barnes <[email protected]> 
wrote:
> It is possible that on that set of hardware a GUI operation is trying 
> to happen before the App has finished initialising - the print 
> statement will slow down the code enough that the initialisation has 
> time to complete. You can try to isolate this by moving print 
> statements a few lines (first try removing/commenting them to see if 
> you get back the problem). It sounds like you might have a candidate 
> for a CallAfter.

I am not quite sure what you mean by "finished initialising", but the 
remainder is spot on. I (re)moved the extra print statements until 
things started to fail again. Looking at the code around the relevant 
print statements I found a number of calls that were a bit too involved 
with using CallAfter(...). I believe they were biting each others 
tails. I rearranged my code a bit, and the problem seems to be gone. 
Thanks everyone!



-- 
You received this message because you are subscribed to the Google Groups "wxPython-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/wxpython-users/1GXRPQ.JZKWLWU1AQIO3%40gmail.com.