This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author PythonInTheGrass
Recipients PythonInTheGrass, brian.curtin, cgohlke, docs@python
Date 2011-01-28.16:38:11
SpamBayes Score 1.7424149e-07
Marked as misclassified No
Message-id <>
Alright. More digging turned up the Tkinter "after" function, aka WM_TIMER for Windowy people like me, and that plus a nonblocking queue get() gets all my drawing operations back into the mainLoop() thread. Voilà, no more crashes.

Let me suggest that page one, sentence one of any Tkinter documentation should begin "Tkinter is not thread safe", with a link to an example of after() and nonblocking get(). I've changed the component to Documentation. This would save a few days for poor sods like me -- I'm used to low level Windows C++ GUI work, where any thread can call any SDK function at any time, and Windows sorts it all out. 

Having to force everything into a single thread, and then poll for my data (*GAG*), is something I thought died in the 80's. Is anyone looking at thread safe GUI libraries?
Date User Action Args
2011-01-28 16:38:12PythonInTheGrasssetrecipients: + PythonInTheGrass, brian.curtin, cgohlke, docs@python
2011-01-28 16:38:12PythonInTheGrasssetmessageid: <>
2011-01-28 16:38:11PythonInTheGrasslinkissue11029 messages
2011-01-28 16:38:11PythonInTheGrasscreate