Ray

@MatthewOwens Thanks for the improvement! I need some time to review this API carefully, to align it with raylib.

@MatthewOwens I know it's been a while since this PR but API has been finally redesigned on commit: https://github.com/raysan5/raylib/commit/99dac5451cad1c45c0a6b1da5c6175a7575f3403

@daipom Thank you very much for all the hard work on this new feature! I couldn't review it carefully yet, probably some function could be renamed but the example looks...

@daipom Hi! It's been quite long since this amazing improvement was proposed, what is the current state? Is there some workaround to allow this feature to be added in raylib?

I just saw there was some update on this PR. I'm keeping it open for a bit longer, it seems lately GLFW is receiving several updates...

@dmlary Yes, that's as expected. `IsKeyPressed()` consumes key polled and polling happens per frame while `GetKeyPressed()` accumulates key presses in an internal queue. At 60 fps it shouldn't be a...

@dmlary I can't reproduce it with my keyboard, it works as expected for me... 🤔

@dmlary Ok, thanks for the detailed explanation, I didn't know about that _mod-tap_ feature of some keyboards. This issue is an edge case and platform-specific (in this case keyboard-specific) so...

@dmlary As per that output, both events (key-down + key-up) are processed in one single frame... I reopen the issue for further review but at a first glance I can't...

@actondev Could this issue be somewhat addressed with newly available key-repeat mechanism? @n77y commented [here](https://github.com/raysan5/raylib/pull/3256#issuecomment-1694340200): > a user could without too much difficulty get around this issue by GetKeyPressed() because...