Revisiting the adage of GUI thread
Nam Nguyen via Tkinter-discuss <[email protected]> Mon, 26 Mar 2018 12:12:31 -0700
| Newsgroups | gmane.comp.python.tkinter |
|---|---|
| Message-ID | <CA+YNSmURnxiFAuvTRMKvKyz7i_Lujd43+Y=5YEz41CtRmy3hzg@mail.gmail.com> |
Hi, The adage often goes something like this: Do all GUI actions in a GUI thread (usually main thread), do I/O in different threads. While it is a good wisdom to apply blanketly, I'm curious about bad outcome from not following that advice. Other than the obvious blocking nature of the event loop, which is why we need threads to work with it, is there any other downside from directly creating, modifying, or destroying Tk objects (such as widgets, variables) in non-GUI threads? Thanks! Nam _______________________________________________ Tkinter-discuss mailing list [email protected] https://mail.python.org/mailman/listinfo/tkinter-discuss
smime.p7s
(application/pkcs7-signature, 4.7 KB) - not displayed