Thanks for your input, nruddock, but I have to confess I hardly understood a word of it.

Quote - Actually it's an optional built-in.

Well, OK. I just don't know what that means. The python.org site appears to be down at the moment, but here is what the cached version says about TkInter:

Quote - "Tkinter is Python's de-facto standard GUI (Graphical User Interface) package. It is a thin object-oriented layer on top of Tcl/Tk.

Tkinter is not the only GuiProgramming toolkit for Python. It is however the most commonly used one"

I don't know if that contradicts what you said or not.

Quote - Not true.
TkInter has always worked fine for Windows version of Poser, but only with P7 did it work for MacOS versions.
The real problem with IDLE is related to threading and also the mechanics of the GUI main loop.

Again, I wish I knew what this meant - the last sentence anyway. Perhaps you can say what the significance of that is vis-a-vis Poser.

Quote - As the interpreter is embedded, and the poser module is a native one, this means that it's going to be tricky to debug as it won't be possible to trace into methods.
Poser also has it's own event loop (which is now reasonably integrated with wxWidgets/wxPython in way that it never was with TkInter) that can present difficulties for debugging, especially where callbacks are triggered by GUI events.

Well, at least I understood the part about "it's going to be tricky to debug."

---

OS: Windows 10 64-bit, Poser: 10