使用Python CustomTkinter实现启动屏时出现无效命令名错误

Error Cause #

The errors stem from pending Tcl/Tk after callbacks that CustomTkinter runs internally for the splash window (like update and check_dpi_scaling). When you call window.destroy() to close the splash screen, these callbacks are still queued to execute. Since the splash window no longer exists, Tcl/Tk can’t locate the widget tied to those commands, resulting in the "invalid command name" error.

Does This Affect the Program? #

No, your main application will run normally because the splash window is fully destroyed before the main app takes over. However, the console errors are unprofessional and could lead to unexpected edge-case behavior if you have other pending callbacks. Fixing them ensures clean execution.

Solutions #

1. Quit the Splash Main Loop Before Destroying the Window #

This is the simplest and most reliable fix. Instead of destroying the splash window immediately, exit its main loop first with window.quit(). This stops all pending after callbacks from running, then you can safely destroy the window.

Modify your main application trigger function like this:

def main_application():
    # Stop the splash window's main loop to cancel pending callbacks
    splash_window.quit()
    # Now destroy the splash window cleanly
    splash_window.destroy()
    
    # Initialize your main application
    main_window = customtkinter.CTk()
    # ... add main app UI elements and logic ...
    main_window.mainloop()

Your splash screen setup would look like this:

import customtkinter as ctk

ctk.set_appearance_mode("dark")
ctk.set_default_color_theme("blue")

splash_window = ctk.CTk()
splash_window.title("Loading")
splash_window.geometry("300x200")

# Add splash content (e.g., loading label)
ctk.CTkLabel(splash_window, text="Initializing App...", font=("Arial", 18)).pack(pady=70)

# Schedule main app to start after 3 seconds
splash_window.after(3000, main_application)

splash_window.mainloop()

2. Cancel Specific Pending Callbacks (Advanced) #

If you need to keep using destroy() directly, you can track and cancel CustomTkinter’s internal after callbacks. However, this requires accessing internal widget IDs, which isn’t straightforward. For most cases, the first solution is sufficient.

3. Hide the Splash Window Instead of Destroying It #

As an alternative, use splash_window.withdraw() to hide the splash screen instead of destroying it immediately. You can call splash_window.destroy() later once the main app is fully initialized. This avoids the callback error but leaves the splash window in memory temporarily.

内容的提问来源于stack exchange，提问作者trizzo