-
Notifications
You must be signed in to change notification settings - Fork 17
Proposed modifications to dev #62
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
Conversation
Like this we got our function name
We could merge a more consistent |
I was thinking about adding an exception type for "vector sizes that do not match". Does it make sense to you ? We seem to be having more and more of these, since bulk and sync commands came around.
The method
Tricky problem. I'll have to think, as it would be best if the library would not let you compile or at least would complain at run time if the method is used with the wrong kind of actuator.
Do you mean that this branch good to merge for you, or do you mean that it needs changes ? |
|
|
The two requested changes were made. I'll carry on with my review and further modifications. Please let me know what need to be done before merging in Also, it would be nice if we could test these changes either with real actuators or with unit a test base. |
|
Any news @PedroDesRobots? |
|
I will merge dev branch and dev-dogoepp, principally for your VecotrEmptyError and VectorSizesDifferError classes for commit 380319a and commits ca8b2a5 will be replaced by abstraction method. |
Notes:
Errors. If there is no matching error type, let us make one.set_goal_positionslacks checks on the actuator max and min angles.protocol_specific_packets.hppIn relation to #61. @PedroDesRobots, comments on these three points ? May I merge ?