-
Notifications
You must be signed in to change notification settings - Fork 276
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add QML Debugging support #1503
Conversation
The project must be rebuilt defining the QT_QML_DEBUG macro. Once that's done, loading the GUI will wait until the debugger is attached to port 40000. QtCreator does this automatically when setting: Projects -> Build -> QML debugging and profiling -> Enable Tested with QtCreator (Qt Quick plugin enabled) and working. Signed-off-by: Matias N. Goldberg <dark_sylinc@yahoo.com.ar>
Codecov Report
@@ Coverage Diff @@
## main #1503 +/- ##
===========================================
- Coverage 63.62% 35.01% -28.62%
===========================================
Files 330 44 -286
Lines 25787 2356 -23431
===========================================
- Hits 16408 825 -15583
+ Misses 9379 1531 -7848 Continue to review full report at Codecov.
|
Thanks for the PR! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think exposing this feature thru a tutorial or an example would be a better idea for usability, because if merged like this the only way users would know about the feature is by reading the source code.
I agree but I am not familiar with the Ruby script. This was a quick and dirty solution that works. The Ruby script rejects cmd arguments it doesn't expect instead of passing them to the application
Updating docs sounds ok. There's no much to it: rebuild gazebo with When launching the gui, stdio will print it's waiting for the debugger to connect to port 40000. |
OK I added gazebosim/docs#251 as documentation that should accompany this new feature. Is it satisfactory? |
Thank you, the doc looks clean, I plan to install QT creator this weekend and test it 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm!
thanks for the PR!
Signed-off-by: Louise Poubel <louise@openrobotics.org>
The project must be rebuilt defining the QT_QML_DEBUG macro.
Once that's done, loading the GUI will wait until the debugger is
attached to port 40000.
QtCreator does this automatically when setting:
Projects -> Build -> QML debugging and profiling -> Enable
Tested with QtCreator (Qt Quick plugin enabled) and working.
Signed-off-by: Matias N. Goldberg dark_sylinc@yahoo.com.ar
🦟 Bug fix
No ticket was created for this issue.
Summary
Troubleshooting QML errors in Javascript code is a PITA without proper tools.
This PR addresses that.
Usually QML debugging is handled automatically by appending the right command line entry.
However IGN is special because it's a so loaded by a ruby script; hence all command line arguments added by QtCreator are lost (and may also result in failure to start).
A quick solution is to hardcode those commands when compiling with
QT_QML_DEBUG
.Checklist
codecheck
passed (See contributing)Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining
Signed-off-by
messages.