Skip to content
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

Handle line crossing events correctly #18

Closed
raintonr opened this issue Jan 13, 2023 · 0 comments · Fixed by #19
Closed

Handle line crossing events correctly #18

raintonr opened this issue Jan 13, 2023 · 0 comments · Fixed by #19
Assignees
Labels
bug Something isn't working

Comments

@raintonr
Copy link
Collaborator

Line crossing events appear to arrive in multipart messages that are not correctly handled.

@raintonr raintonr self-assigned this Jan 13, 2023
raintonr added a commit that referenced this issue Jan 14, 2023
@raintonr raintonr linked a pull request Jan 14, 2023 that will close this issue
raintonr added a commit that referenced this issue Jan 14, 2023
…e-crossing-events-correctly

#18 Fix multipart message handling
@raintonr raintonr added the bug Something isn't working label Jan 20, 2023
raintonr added a commit that referenced this issue Jan 24, 2023
-   (Robin Rainton) Added configuration for alarm timeout ([#16](#16)).
-   (Robin Rainton) Fixed multipart message handling for line crossing/field detection, etc ([#18](#18)).
-   (Robin Rainton) Optionally save XML/images & send events using `sendTo` to other adapters ([#20](#20) & [#26](#26)).
-   (Robin Rainton) Added info.connection state ([#22](#22)).
-   (Robin Rainton) Handle cases where `TargetRect` is specified in decimals between zero & one ([#24](#24)).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant