Details
-
Bug
-
Resolution: Out of scope
-
Not Evaluated
-
None
-
5.15.7, 6.4.2
-
None
Description
On creation of QUiLoader object it automatically loads all designer plugins listed in QApplication::libraryPaths(). And there is no way to prevent it from doing so besides altering global property QApplication::libraryPaths itself (which is a quite ugly workaround). Subsequent calls to QUiLoader::clearPluginPaths() won't unload the plugin and its dependencies either.
The more prominent issues arise when a plugin or its dependencies produces some undesireble behaviour upon load. This was a reason for a FreeCAD bug[1].
------
Could you please add a normal way to create a QUiLoader object without loading any external plugins besides mending with, i.e add a second constructor with a list of pluginPaths.
------