PyQt5转PySide2：多类加载UI文件功能适配求助

Got it, let's walk through how to fully migrate your Python 3.6 app from PyQt5 to PySide2, with support for loading UI files across multiple classes, and implementing interactions like opening a second window from a button click. I'll cover key migration differences and provide a complete working example tailored to your needs.

Key Migration Differences to Note #

First, let's get the basics out of the way—these are the critical changes between PyQt5 and PySide2:

• Module Imports: Replace PyQt5 with PySide2 in all import statements (e.g., from PySide2.QtWidgets import ... instead of PyQt5).
• UI Loading: PyQt5 uses uic.loadUi(), while PySide2 uses QtUiTools.QUiLoader() for dynamic UI loading. Alternatively, you can convert your .ui files to Python modules with the pyside2-uic command (more on that later).
• Signals/Slots: PyQt5's pyqtSignal/pyqtSlot become Signal/Slot in PySide2 (imported from PySide2.QtCore). For basic connections, though, you can often use the same syntax as PyQt5 without changing much.
• Resource Files: Replace pyrcc5 with pyside2-rcc to convert .qrc files to Python modules.

Complete Implementation Example #

Let's assume you have two UI files created in Qt Designer 5.9.4:

• main_window.ui: Contains a button named pushButton_open_second and a table widget named tableWidget.
• second_window.ui: Contains its own table widget (also named tableWidget for this example).

1. Main Window Class (Loads main_window.ui) #

This class handles the main UI, initializes the table, and triggers the second window when the button is clicked.

from PySide2.QtWidgets import QMainWindow, QApplication, QTableWidgetItem
from PySide2.QtUiTools import QUiLoader

class MainWindow(QMainWindow):
    def __init__(self):
        super().__init__()
        self.load_ui()
        self.bind_events()
        self.init_main_table()

    def load_ui(self):
        # Initialize the UI loader and load the main window UI
        loader = QUiLoader()
        # Replace with the actual path to your main_window.ui file
        self.ui = loader.load("main_window.ui", self)
        self.setCentralWidget(self.ui)

    def bind_events(self):
        # Connect the button click to the second window opener
        self.ui.pushButton_open_second.clicked.connect(self.open_second_window)

    def init_main_table(self):
        # Example: Populate the main window's table widget
        self.ui.tableWidget.setRowCount(3)
        self.ui.tableWidget.setColumnCount(2)
        
        # Add sample data
        self.ui.tableWidget.setItem(0, 0, QTableWidgetItem("User ID"))
        self.ui.tableWidget.setItem(0, 1, QTableWidgetItem("Username"))
        self.ui.tableWidget.setItem(1, 0, QTableWidgetItem("101"))
        self.ui.tableWidget.setItem(1, 1, QTableWidgetItem("JohnDoe"))
        self.ui.tableWidget.setItem(2, 0, QTableWidgetItem("102"))
        self.ui.tableWidget.setItem(2, 1, QTableWidgetItem("JaneSmith"))

    def open_second_window(self):
        # Create and show the second window
        # Store it as an instance attribute to avoid garbage collection (prevents window from closing immediately)
        self.second_window = SecondWindow()
        self.second_window.show()

2. Second Window Class (Loads second_window.ui) #

This is an independent class for the secondary window, with its own table initialization logic.

from PySide2.QtWidgets import QWidget, QTableWidgetItem
from PySide2.QtUiTools import QUiLoader

class SecondWindow(QWidget):
    def __init__(self):
        super().__init__()
        self.load_ui()
        self.init_second_table()

    def load_ui(self):
        loader = QUiLoader()
        # Replace with the actual path to your second_window.ui file
        self.ui = loader.load("second_window.ui", self)

    def init_second_table(self):
        # Example: Populate the second window's table widget
        self.ui.tableWidget.setRowCount(2)
        self.ui.tableWidget.setColumnCount(3)
        
        self.ui.tableWidget.setItem(0, 0, QTableWidgetItem("Product ID"))
        self.ui.tableWidget.setItem(0, 1, QTableWidgetItem("Name"))
        self.ui.tableWidget.setItem(0, 2, QTableWidgetItem("Price"))
        self.ui.tableWidget.setItem(1, 0, QTableWidgetItem("P001"))
        self.ui.tableWidget.setItem(1, 1, QTableWidgetItem("Wireless Mouse"))
        self.ui.tableWidget.setItem(1, 2, QTableWidgetItem("$29.99"))

3. Main Execution Script #

This is the entry point of your application:

if __name__ == "__main__":
    import sys
    app = QApplication(sys.argv)
    main_window = MainWindow()
    main_window.show()
    sys.exit(app.exec_())

Alternative: Convert UI Files to Python Modules #

If you prefer static UI loading (for better code completion and fewer runtime errors), convert your .ui files using the pyside2-uic command-line tool:

# Convert main_window.ui to a Python module
pyside2-uic main_window.ui -o ui_main_window.py

# Convert second_window.ui
pyside2-uic second_window.ui -o ui_second_window.py

Then modify your classes to inherit from the generated UI classes:

# MainWindow example with static UI loading
from PySide2.QtWidgets import QMainWindow, QTableWidgetItem
from ui_main_window import Ui_MainWindow

class MainWindow(QMainWindow, Ui_MainWindow):
    def __init__(self):
        super().__init__()
        self.setupUi(self)  # Initialize the UI from the generated module
        self.bind_events()
        self.init_main_table()

    # Rest of the methods remain the same...

Important Notes #

• Window Lifecycle: Always store child windows as instance attributes (like self.second_window) instead of local variables—this prevents Python's garbage collector from deleting the window immediately after it's created.
• Control Names: Ensure the names of your UI controls (buttons, tables, etc.) match exactly between Qt Designer and your Python code. Typos will cause attribute errors.
• Python 3.6 Compatibility: PySide2 supports Python 3.6, so you shouldn't run into version conflicts as long as you install a compatible PySide2 version (e.g., pip install pyside2==5.15.2.1—this version works well with Python 3.6).

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