Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. QML and Qt Quick
  4. Debugging QML parsing
Forum Updated to NodeBB v4.3 + New Features

Debugging QML parsing

Scheduled Pinned Locked Moved Unsolved QML and Qt Quick
3 Posts 2 Posters 509 Views 1 Watching
  • 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.
  • N Offline
    N Offline
    nminkov
    wrote on 31 Dec 2019, 12:24 last edited by
    #1

    Hi,
    I am new to QT Quick and trying to setup basic functionalities.

    I am using Visual Studio 2019 + QT VS Tools .

    When there is an error in the QML file that I try to load in my program, it usually ends with "Access violation" or obscure assertion in QT, with almost no info to actually find what the issue is.

    If I check the QML file in QT Creator, usually, but not always it will give me clues of the simple syntax error that it caused it, or if I manage to run in it even runtime info in QML debug console like "qrc:​/​main.​qml:​3 module "​QtQuick.​Controls"​ version 2.​14 is not installed".

    Now running my project in QT Creator is not practical. How do I access all the QML syntax or runtime error that are visible in QT Creator from the C++ side on runtime? I've already defined QT_QML_DEBUG, QT_DECLARATIVE_DEBUG, QML_IMPORT_TRACE visual studio project, and I can actually debug step by step the QML files.

    Thanks

    1 Reply Last reply
    0
    • K Offline
      K Offline
      Kiranachari Shilpi
      wrote on 31 Dec 2019, 14:47 last edited by
      #2

      Hi ,
      May I know which version of Qt Creator you used...

      N 1 Reply Last reply 9 Jan 2020, 09:07
      0
      • K Kiranachari Shilpi
        31 Dec 2019, 14:47

        Hi ,
        May I know which version of Qt Creator you used...

        N Offline
        N Offline
        nminkov
        wrote on 9 Jan 2020, 09:07 last edited by
        #3

        @Kiranachari-Shilpi QT Creator 4.11. However I would like to avoid using it for debugging. I would like to capture and show the errors internally. E.g. will also need it for changing UI on the fly with live QML editing.

        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