View Single Post
Old 05-28-2025, 12:00 PM   #18
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,914
Karma: 6120478
Join Date: Nov 2009
Device: many
Quote:
Originally Posted by DiapDealer View Post
I'd prefer to reduce the amount of potentially unnecessary import bloat. Users still needed to import QtWebEngine from plug_utils into their plugin anyway (to get the PySide or PQt5 version), so I figure directly importing it from PySide6 should be no great hardship. In fact, I would rather they took over the importing of PySide6 modules themselves anyway. Just use plugin_utils_light for the wrapped QApplication functionality.
Okay, for my limited use case of inline QFileDialog static functions, and no translations I will change to import QtWidgets directly from PySide. I will still keep the plugin_utils_light.py code inside the plugin in case I move to adding translation support at some point (which I probably should).

Thanks!
KevinH is online now   Reply With Quote