Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Qt Creator and other tools
  4. Correct usage of QML_DESIGNER_IMPORT_PATH and QML_IMPORT_PATH

Correct usage of QML_DESIGNER_IMPORT_PATH and QML_IMPORT_PATH

Scheduled Pinned Locked Moved Unsolved Qt Creator and other tools
qt creatordesigner plugin
2 Posts 2 Posters 931 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A Offline
    A Offline
    Andreas Schacherbauer
    wrote on 18 Jun 2020, 15:27 last edited by Andreas Schacherbauer
    #1

    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_PATH should 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_PATH path to point to the desinger directory in our QmlPlugin but nothing happens.
    Is QML_DESIGNER_IMPORT_PATH actually meant to replace a production .qml with a design mode specific?

    Thx!

    1 Reply Last reply
    0
    • A Offline
      A Offline
      afalsa
      wrote on 3 Apr 2022, 18:51 last edited by
      #2

      Hello @Andreas-Schacherbauer ,

      did you find out any solution?

      1 Reply Last reply
      0

      • Login

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Users
      • Groups
      • Search
      • Get Qt Extensions
      • Unsolved