Correct usage of QML_DESIGNER_IMPORT_PATH and QML_IMPORT_PATH
Andreas Schacherbauer last edited by Andreas Schacherbauer
Hi, we have a QmlPlugin that ships as .so file togehter with .qml files. When building and running the projects, everything is fine. Now we want to add support for the Designer Mode in Qt Creator. Following https://doc.qt.io/qtcreator/creator-qml-modules-with-plugins.html, everything is fine, Designer can find the qml files and load the shared libraries. Since our .qml components require some C++ backend, we want to mock them now. As far as I understood,
QML_DESIGNER_IMPORT_PATHshould help here as it should allow us to replace the original .qml file with an alternative implementation for the designer?! We set the
QML_DESIGNER_IMPORT_PATHpath to point to the
desingerdirectory in our QmlPlugin but nothing happens.
QML_DESIGNER_IMPORT_PATHactually meant to replace a production .qml with a design mode specific?
afalsa last edited by
Hello @Andreas-Schacherbauer ,
did you find out any solution?