-
Notifications
You must be signed in to change notification settings - Fork 70
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
Issue MID 0245 #77
Labels
Comments
Hello Roberto, good to hear that the library is helping you.
|
Rickedb
added a commit
that referenced
this issue
Sep 23, 2021
Hello Henrique
thank you for your clarification
Have a nice day
Roberto Guerzoni
Da: Henrique Dal Bello ***@***.***>
Inviato: giovedì 23 settembre 2021 22:42
A: Rickedb/OpenProtocolInterpreter ***@***.***>
Cc: Roberto Guerzoni ***@***.***>; Author ***@***.***>
Oggetto: Re: [Rickedb/OpenProtocolInterpreter] Issue MID 0245 (#77)
Hello Roberto, good to hear that the library is helping you.
Answering your questions:
1. Offset field does have a bug and it was probably a copy + paste issue 😂
2. About User data field: no, it's not obligatory to fill with 200 chars. In addition, the library (still) does not watch over the minimun and maximun values.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#77 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AR2ZK4K5GYSSN4VK3UAUH7TUDOGINANCNFSM5EUMCOCA>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm using your excellent library to realize an Open Protocol Simulator. During my development i noticed an issue into MID 0245. I suppose the issue derive from a wrong cut and paste.
In my opinion the code should be fixed into this point
I'm not sure the USER_DATA field must be filled to 200 chars.
The documentation say:
Can you confirm the need of that padding?
Have a nice day
Roberto Guerzoni
The text was updated successfully, but these errors were encountered: