Program Architecture

[ShayBox]

So, although switching to Pyside6 (Qt6) is as easy as swapping the packages and import statements, there's a larger issue.

There's segmentation faults from the update_ui thread, updating ui elements from a separate thread is not thread-safe anymore.

This would require either locking every update loop, and adding some sleep delay, which would noticeably slow down updating and responsiveness, or redesign the entire update thread to use QThread and signal/emit to the main thread and update the ui from the main thread.

For now I'm going to keep the project on PySide2, but at some point as KDE and other projects move away from qt5 this will need to be updated.

[ShayBox]

I released 1.0.0 with support for PySide2 (Qt5) and PySide6(Qt6), completely rewritten and more thread safe, using QThread instead of threading.Thread

[ShayBox]

I switched the program to use spyder-ide/qtpy for cross-qt code, however pyside2/6 doesn't support signals/slots on loadUi from .ui files, which was why I used uic to compile .ui to .py, however pyqt5/6 does, so until pyside supports that this program won't work with pyside2/6 without switching it back to using an intermediate compiled python file.