On Wed, Jun 06, 2018 at 12:55:25PM -0700, Tim Jones wrote: . . . > > On Jun 6, 2018, at 11:56 AM, Mark Roseman <m...@markroseman.com> wrote: > > > > The best part of this, at least as far as stability goes, is that Tcl > > controls the timing of the calls into Tkinter, so that it will only make > > them when it’s “safe” to do so, from a thread it expects to do so from, > > etc. Given that Tcl has the stricter restrictions on what can be called > > when and from where, this seems like a win. On the Tkinter side, it never > > has to worry about if it’s safe to call into Tcl. > > > > (The one exception to this is probably application startup, i.e. before we > > hit mainloop, where Tkinter would just call directly into Tcl. It may be a > > reasonable restriction to say that you have to make Tkinter calls from the > > originating thread if they’re made before you hit mainloop). > > > > To me this appears like it should be feasible. Any thoughts? > > > > Mark > > Such a change alone would bring me back to Python and TKInter for UI apps. . . . Me, too!
That is, this change sounds to me: * feasible * overdue * welcome. I only wish I had availability to offer to help. I actually was working on the Tcl event loop in '96-97 ... _______________________________________________ Tkinter-discuss mailing list Tkinter-discuss@python.org https://mail.python.org/mailman/listinfo/tkinter-discuss