如何用Tkinter将命令行交互脚本转为GUI按钮交互？

Got it, let's convert those command-line prompts into interactive Tkinter button-based dialogs. Here's a step-by-step solution that ties your existing logic to the GUI, with proper flow between the two prompts:

Step 1: Refactor your core logic to work with GUI inputs #

First, update your questions.py (the core script) to remove the input() calls, and instead make the functions trigger GUI dialogs. We'll use Tkinter's Toplevel windows for custom button prompts, which aligns with your request to replace text input with buttons.

Updated questions.py:

from colorama import init, Fore, Back, Style
import commands
import config
import sys
import tkinter as tk
from tkinter import messagebox

# Coloroma autoreset
init(autoreset=True)

def on_db_check_choice(choice, dialog_window):
    # Handle database check choice and close the dialog
    dialog_window.destroy()
    if choice.lower() == 'y':
        commands.db_download()
    # Move to the next step: client selection
    show_client_selection()

def show_db_check_dialog(parent_window):
    # Create a focused window for the database check prompt
    db_dialog = tk.Toplevel(parent_window)
    db_dialog.title("Database Check")
    db_dialog.geometry("300x100")
    db_dialog.resizable(False, False)
    # Keep dialog on top of the main window
    db_dialog.transient(parent_window)

    # Question label
    tk.Label(db_dialog, text="Check for new databases?", padx=10, pady=10).pack()

    # Button container
    btn_frame = tk.Frame(db_dialog)
    btn_frame.pack(pady=5)

    # Yes/No buttons with action handlers
    tk.Button(btn_frame, text="Yes", command=lambda: on_db_check_choice('y', db_dialog)).grid(row=0, column=0, padx=10)
    tk.Button(btn_frame, text="No", command=lambda: on_db_check_choice('n', db_dialog)).grid(row=0, column=1, padx=10)

def on_client_choice(choice, dialog_window):
    # Handle client selection and close the dialog
    dialog_window.destroy()
    if choice.lower() == 'j':
        config.client = 'japan'
    elif choice.lower() == 'g':
        config.client = 'global'
    # Confirm completion to the user
    messagebox.showinfo("Setup Complete", f"Client set to {config.client.capitalize()}! Your bot is ready to launch.")
    # Add your bot launch code here if needed

def show_client_selection():
    # Create a window for client selection
    client_dialog = tk.Toplevel()
    client_dialog.title("Client Selection")
    client_dialog.geometry("300x100")
    client_dialog.resizable(False, False)

    # Question label
    tk.Label(client_dialog, text="JP or GLB?", padx=10, pady=10).pack()

    # Button container
    btn_frame = tk.Frame(client_dialog)
    btn_frame.pack(pady=5)

    # JP/GLB buttons with action handlers
    tk.Button(btn_frame, text="JP", command=lambda: on_client_choice('j', client_dialog)).grid(row=0, column=0, padx=10)
    tk.Button(btn_frame, text="GLB", command=lambda: on_client_choice('g', client_dialog)).grid(row=0, column=1, padx=10)

Step 2: Update your main Tkinter window to trigger the flow #

Modify your main script to start the interactive flow when the "Launch bot" button is clicked. We'll tie the dialogs to the main window to keep the app organized.

Updated main script:

import tkinter as tk
import questions

def start_bot_setup():
    # Kick off the first prompt: database check
    questions.show_db_check_dialog(top)

# Initialize main window
top = tk.Tk()
top.title("Bot Launcher")
top.geometry("200x100")
top.resizable(False, False)

# Launch button that starts the full setup flow
launch_btn = tk.Button(top, text="Launch bot", command=start_bot_setup)
launch_btn.pack(pady=30)

top.mainloop()

Key Details to Note #

• Non-blocking Dialogs: We use Toplevel windows instead of input() so the main GUI stays responsive, which is critical for Tkinter apps.
• Flow Continuity: After the user selects Yes/No for the database check, the script automatically launches the client selection dialog—mirroring the original command-line workflow but in a graphical format.
• Lambda Handlers: Lambdas let us pass the user's choice and dialog window reference to the handler functions, so we can cleanly close the dialog after the selection is made.
• Config Compatibility: The config.client variable is updated exactly like in your original script, so your bot's core logic will work without changes once setup is done.

Optional Enhancements #

• Add a loading label or progress bar while commands.db_download() runs (since it might take time).
• Disable the main window's "Launch bot" button while dialogs are open to prevent duplicate setup flows.
• Add error handling for commands.db_download() failures, using messagebox.showerror() to alert the user.

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