-
Notifications
You must be signed in to change notification settings - Fork 50
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
new_protocol has no way to set endianess #63
Comments
So, I tried my fix and change the method to the following:
This maintains backward compatibility and appears to fix the issue I was having. My server now appears to be getting bytes in the correct order. (pending further testing) I can now write this: Would be awesome if you could apply this to your great library. Thanks, |
Yeah, the endiannes thing was usable only by extending the base library. (It has been used like that) Thanks for the pull request, I will try to review it soon. I havent had time to look at this library for a long time... :( |
In the function
new_protocol
The line
self._init_new_message_stack(Protocol(protocol_name, library=self))
gives no option to set the Protocol constructor option forlittle_endian
. Neither does thenew_protocol
method.So, there does not seem to be a way to use the robot api, and have this little_endian feature. It would be very useful if the endian setting could be set from the robot api.
At least, that's how it looks to me atm.
Thanks for reviewing this issue.
Cheers,
Matt
The text was updated successfully, but these errors were encountered: