-
Notifications
You must be signed in to change notification settings - Fork 195
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
Desired torque decimals are not displayed in the motorgui if the torque control mode is set #3118
Comments
|
If someone can point me the code I should check I can try to fix it |
I guess somewhere around yarp/src/yarpmotorgui/jointitem.cpp Lines 1145 to 1176 in bde9cd2
|
Reading the code, I guess there is already a similar functionality if you go in Slider ---> Torque Options. |
Cool! Still, according to your picture, the number of slider decimal digits seems to be available oly for position control |
So I checked the code and there are three possible solutions: The easiest solutionModify the following line yarp/src/yarpmotorgui/sliderWithTarget.h Line 23 in bde9cd2
intermediate solutionadd a function to change the slide for the torque (and velocity at this point) and modify
and
to set the decimal number to an hardcoded value complex solutionmodify the GUI and all the signal slots to have the possibility to set the number of digits. Indeed they are set only for position control in yarp/src/yarpmotorgui/jointitem.cpp Line 1050 in bde9cd2
|
Hi @traversaro, Do you have any updates or ideas on how to proceed with this task? |
I think the easy solution proposed by Giulio Romualdi make sense. I think it make sense to have 1 or 2 as default number of decimal (rather then 0), can you try if that works? |
Describe the bug
I noticed that the desired torque are treated as integer in the motorgui
To Reproduce
Start the motorgui and set on joint in torque
Expected behavior
It would be nice to have three decimal as the position control
Screenshots
Configuration (please complete the following information):
Additional context
cc @GiulioRomualdi
The text was updated successfully, but these errors were encountered: