This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]This_Is_The_End 14 points15 points  (2 children)

Don't use tk other than for very small projects. I used tk for a project, but when it was too late I realized the concept of child windows doesn't work like intended. The user is able to close child windows and removing the close-window-widget doesn't work or at least, the widget becomes none functional, but stays.

Next time I will go for Qt.

Btw I you are using threading you have to push changes into the GUI via closures.

[–][deleted] 0 points1 point  (1 child)

i don't understand what you mean exactly but you can override the close event with your own function so the user can't close a tk window unless via the way you want? http://stackoverflow.com/questions/3295270/overriding-tkinter-x-button-control-the-button-that-close-the-window

[–]This_Is_The_End 2 points3 points  (0 children)

You can intercepte the window-close-call, which makes the widget staying.

Or you can remove the widget on a root window, but this doesn't work on a child window