-
-
Notifications
You must be signed in to change notification settings - Fork 469
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
Allow force and torque in Wrench to be scaled separately #862
Allow force and torque in Wrench to be scaled separately #862
Conversation
Thanks for the pull request, the changes look ok, but I'm going to release any more Groovy versions of rviz. Can you please open the pull request against the |
+1 |
I'm going to merge this into groovy-devel, but I will not be releasing a new version. |
Allow force and torque in Wrench to be scaled separately
…g_indigo Forward port of pull request #862 to indigo-devel
And we'll have to forward-port it to latest versions, right?
|
Yeah, #870 is for indigo, I'll back port to hydro when I do the next release. |
I also back ported @chapulina's commit fixing the indention up: d24eadc |
Thank you so much! |
…ization#867) These resource files support relative paths from their directory, so we should override the default paths for UNIX and WIN32 to act like APPLE, where relative paths are used by default. This should be a pretty safe thing to do because the absolute paths currently in these locations are actually to the staging in the project's build directory, which isn't available unless building from source. Signed-off-by: Scott K Logan <logans@cottsay.net> (cherry picked from commit 5c54f57ba409b1a096f9310a9b75d67731137b39) Co-authored-by: Scott K Logan <logans@cottsay.net>
since force and torque are different quantities, the units of their scalings are different (meters per Newton and meters per Newton-meter, respectively), and so they should really have separate scalings. Practically, the torques in my Wrench are usually much smaller than the forces if I use the same scaling.
I am on Groovy, but it looks like this patch can apply to all releases up to present.