CustomTkinter icon indicating copy to clipboard operation
CustomTkinter copied to clipboard

invalid command name

Open H15STER opened this issue 1 year ago • 3 comments

Hi, I'm making my application with multiple windows. When the user clicks on the "log in" button, the window closes via self.destroy(), and another window opens, while writing this in the console:

invalid command name "332041600update" while executing "332041600update" ("after" script) invalid command name "63023232check_dpi_scaling" while executing "63023232check_dpi_scaling" ("after" script) invalid command name "332184896_click_animation" while executing "332184896_click_animation" ("after" script)

This does not affect the operation of the program, but the user will not be pleased to look at it every time

H15STER avatar Feb 14 '24 11:02 H15STER

Description:

This is caused when you are destroying the window first and then creating another window. something like this:

window.destroy()
anotherwindow.mainloop()

Solution:

The solution for this is to use CTkTopLevel instead of creating a new window, or you can simply move back and fourth in frames created for each window.

AshhadDevLab avatar Feb 19 '24 09:02 AshhadDevLab

Thanks

пн, 19 февр. 2024 г., 13:57 Ashhad Ahmed @.***>:

Description:

This is caused when you are destroying the window first and then creating another window. something like this:

window.destroy()anotherwindow.mainloop()

Solution:

The solution for this is to use CTkTopLevel instead of creating a new window, or you can simply move back and fourth in frames created for each window.

— Reply to this email directly, view it on GitHub https://github.com/TomSchimansky/CustomTkinter/issues/2269#issuecomment-1952088937, or unsubscribe https://github.com/notifications/unsubscribe-auth/APTOLNJK6VHQYGD5X5KZAXLYUMOXNAVCNFSM6AAAAABDIEJFYCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJSGA4DQOJTG4 . You are receiving this because you authored the thread.Message ID: @.***>

H15STER avatar Feb 19 '24 10:02 H15STER

Thanks пн, 19 февр. 2024 г., 13:57 Ashhad Ahmed @.>: Description: This is caused when you are destroying the window first and then creating another window. something like this: window.destroy()anotherwindow.mainloop() Solution: The solution for this is to use CTkTopLevel instead of creating a new window, or you can simply move back and fourth in frames created for each window. — Reply to this email directly, view it on GitHub <#2269 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/APTOLNJK6VHQYGD5X5KZAXLYUMOXNAVCNFSM6AAAAABDIEJFYCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJSGA4DQOJTG4 . You are receiving this because you authored the thread.Message ID: @.>

if this answers your question mark the question as solved!

AshhadDevLab avatar Feb 19 '24 10:02 AshhadDevLab