Qt Creator, pyside6, QML debuggger
-
wrote on 3 Oct 2023, 04:34 last edited by CKurdu 10 Mar 2023, 04:34
Hello everyone,
I can't find enough information about how to work the QML debugger in a PySide6 project.
This is what I found that is related a C++ Qt project.
[https://doc.qt.io/qtcreator/creator-debugging-qml.html]
I tried the below link and also tried "attach to QML port" but It didn't work.
https://doc.qt.io/qtforpython-6/overviews/qtquick-debugging.html
-
Hello everyone,
I can't find enough information about how to work the QML debugger in a PySide6 project.
This is what I found that is related a C++ Qt project.
[https://doc.qt.io/qtcreator/creator-debugging-qml.html]
I tried the below link and also tried "attach to QML port" but It didn't work.
https://doc.qt.io/qtforpython-6/overviews/qtquick-debugging.html
-
I realized that in the console it says
QML Debugger: Ignoring "-qmljsdebugger=port:12345,block". Debugging has not been enabled.Should I compile PySide6 or is there a version debugging enabled?
Window 11 64bit
wrote on 3 Oct 2023, 07:06 last edited byWhen I run from Qt Creator, it doesn't appear. But I cannot connect to the port for QML debugging.
-
wrote on 19 Nov 2023, 17:29 last edited by
I've been trying to solve this for a few days. There is no issues with the output coming to console in VsCode but QT Creator with pyside6 simply doesn't work.
-
wrote on 20 Nov 2023, 12:33 last edited by
QML debugging needs to be enabled in the app by something like
from PySide6.QtQml import QQmlDebuggingEnabler QQmlDebuggingEnabler.enableDebugging(True)This should be removed when shipping the code though for security reasons.
-
QML debugging needs to be enabled in the app by something like
from PySide6.QtQml import QQmlDebuggingEnabler QQmlDebuggingEnabler.enableDebugging(True)This should be removed when shipping the code though for security reasons.
wrote on 21 Nov 2023, 05:13 last edited by@friedemannkleint I'll try it out and get back tomorrow. Thanks!
-
QML debugging needs to be enabled in the app by something like
from PySide6.QtQml import QQmlDebuggingEnabler QQmlDebuggingEnabler.enableDebugging(True)This should be removed when shipping the code though for security reasons.
wrote on 21 Nov 2023, 14:15 last edited by@friedemannkleint said in Qt Creator, pyside6, QML debuggger:
QQmlDebuggingEnabler.enableDebugging(True)
Unfortunately this made no difference actually. When you use QTCreator to run in debug mode you will get this message.
Message might seem self explanatory but turns out QT Creator does not have this option inside of the "Build" under project.
I've searched for this option all over else where through out the program to no avail.
"Run" does have it, but makes no difference since it wants it in both options checked, but it's impossible to do so for pyside6.
-
@friedemannkleint said in Qt Creator, pyside6, QML debuggger:
QQmlDebuggingEnabler.enableDebugging(True)
Unfortunately this made no difference actually. When you use QTCreator to run in debug mode you will get this message.
Message might seem self explanatory but turns out QT Creator does not have this option inside of the "Build" under project.
I've searched for this option all over else where through out the program to no avail.
"Run" does have it, but makes no difference since it wants it in both options checked, but it's impossible to do so for pyside6.
wrote on 21 Nov 2023, 15:41 last edited by jlw_4049Good news is VSCode has no problem at least showing the output in the terminal by default where as QT Creator fails to show anything of relevance at all as far as debugging. Granted this is due to just running the script via
python main.pyand if I did this manually in QT Creator it would have the same output.
-
Good news is VSCode has no problem at least showing the output in the terminal by default where as QT Creator fails to show anything of relevance at all as far as debugging. Granted this is due to just running the script via
python main.pyand if I did this manually in QT Creator it would have the same output. -
wrote on 28 Nov 2023, 07:28 last edited by
Whether Qt Creator shows sth in the console might be influenced by the buffered output option of python3 (pass -u to python3 [-u : force the stdout and stderr streams to be unbuffered, or set PYTHONUNBUFFERED=1]). This should also be available in the run settings. Are these breakpoints from C++ maybe - Qt Creator sometimes remembers breakpoints.