Skip to content
  • 0 Votes
    1 Posts
    65 Views
    No one has replied
  • 0 Votes
    8 Posts
    2k Views
    MesrineM

    @lucast

    Thanks, indeed it aligns better with the new design.
    I will try to use loadFromModule API from now on
    According to this will improve compilation time when changing qml files, that is something I was looking for.

  • 0 Votes
    3 Posts
    1k Views
    QjayQ

    @JoeCFD QML file code below. I haven't edited it at all.

    QT += quick CONFIG += c++11 # The following define makes your compiler emit warnings if you use # any Qt feature that has been marked deprecated (the exact warnings # depend on your compiler). Refer to the documentation for the # deprecated API to know how to port your code away from it. DEFINES += QT_DEPRECATED_WARNINGS # You can also make your code fail to compile if it uses deprecated APIs. # In order to do so, uncomment the following line. # You can also select to disable deprecated APIs only up to a certain version of Qt. #DEFINES += QT_DISABLE_DEPRECATED_BEFORE=0x060000 # disables all the APIs deprecated before Qt 6.0.0 SOURCES += \ main.cpp RESOURCES += qml.qrc # Additional import path used to resolve QML modules in Qt Creator's code model QML_IMPORT_PATH = # Additional import path used to resolve QML modules just for Qt Quick Designer QML_DESIGNER_IMPORT_PATH = # Default rules for deployment. qnx: target.path = /tmp/$${TARGET}/bin else: unix:!android: target.path = /opt/$${TARGET}/bin !isEmpty(target.path): INSTALLS += target
  • 0 Votes
    3 Posts
    249 Views
    A

    @ankou29666 That did not work too. Also, I do have a qrc path