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

Move "non-binary" event processing to its own thread #17

Open
dogtopus opened this issue Aug 21, 2021 · 0 comments
Open

Move "non-binary" event processing to its own thread #17

dogtopus opened this issue Aug 21, 2021 · 0 comments
Labels
bug Something isn't working

Comments

@dogtopus
Copy link
Owner

Turns out RescheduleableAlarm.reschedule is so heavy that it's not suitable for hot loops like tween scheduling. We should probably move it to its own thread instead.

(This might cause one-shot events to fall off sync with "non-binary" events but it should be fine since timing critical events like IMU will still be synchronized.)

@dogtopus dogtopus added the bug Something isn't working label Aug 21, 2021
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

No branches or pull requests

1 participant