We do not need to account for drift when we USE_WINDOWS_EVENTS by pierreluctg · Pull Request #1666 · hardbyte/python-can

Skip to content

Navigation Menu

Sign in

Appearance settings

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up

Appearance settings

Conversation

@pierreluctg

Copy link

Collaborator

@pierreluctg pierreluctg commented

Sep 27, 2023

edited

Loading

When using USE_WINDOWS_EVENTS the waitable timer will be fired at fixed rate, we do not need to account for the drift.
The change makes it wait for the timer to be in signaled state only.
Previous code was causing multiple frames to be send back to back without delay.

@pierreluctg pierreluctg marked this pull request as ready for review

September 27, 2023 23:48

@pierreluctg pierreluctg changed the title We do not need to account for drift when USE_WINDOWS_EVENTS We do not need to account for drift when we USE_WINDOWS_EVENTS

Sep 28, 2023

@pierreluctg

Copy link

Collaborator Author

@zariiii9003 please review

@pierreluctg pierreluctg merged commit 3c3f123 into develop

Oct 2, 2023

@pierreluctg pierreluctg deleted the USE_WINDOWS_EVENTS branch

October 2, 2023 22:22

@pierreluctg pierreluctg added this to the Next Release milestone

Oct 2, 2023

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@zariiii9003 zariiii9003 zariiii9003 approved these changes

Assignees

No one assigned

Projects

None yet

Milestone

Next Release

Development

Successfully merging this pull request may close these issues.

2 participants

@pierreluctg @zariiii9003