Skip to content

Input events are queued without proper flushing or debouncing, causing residual movement after rapid key presses #20

Description

@itssimmons

When the left and right arrow keys are pressed repeatedly in rapid succession, input events accumulate in the internal queue. After the user ceases pressing keys, the queued inputs continue to be processed, causing the piece to move autonomously until the backlog is exhausted.


This repo is using Opire - what does it mean? 👇
💵 Everyone can add rewards for this issue commenting /reward 100 (replace 100 with the amount).
🕵️‍♂️ If someone starts working on this issue to earn the rewards, they can comment /try to let everyone know!
🙌 And when they open the PR, they can comment /claim #20 either in the PR description or in a PR's comment.

🪙 Also, everyone can tip any user commenting /tip 20 @itssimmons (replace 20 with the amount, and @itssimmons with the user to tip).

📖 If you want to learn more, check out our documentation.

Activity

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

Metadata

Metadata

Assignees

Labels

bugSomething isn't workinggood first issueGood for newcomers

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions