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

Document buffering behavior for events #876

Open
thurn opened this issue Apr 5, 2024 · 0 comments
Open

Document buffering behavior for events #876

thurn opened this issue Apr 5, 2024 · 0 comments

Comments

@thurn
Copy link

thurn commented Apr 5, 2024

The documentation for event::read doesn't discuss buffering behavior: https://docs.rs/crossterm/0.27.0/crossterm/event/fn.read.html, i.e. what happens if multiple events have come in since the last time you checked for events.

Based on briefly looking at the source code I think the behavior is to keep the most recent 32 events and silently drop the rest, returning them in order from oldest to newest. But I could also be reading it completely wrong.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant