You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Glutin currently supports key press events and key release events. But (on Windows at least), key press events correspond to the virtual key presses that the OS does, including the repeated presses that occur when you hold the key down. I would really like to be able to get actual physical key down events as well, and distinguish between "presses" and key down events. At the moment, you can get more key press events than release events due to press repetition. I need this distinction for integration with the Chromium Embedded Framework, which has three types of key event - up, down and press.
The ElementState enum currently contains Pressed and Released. Ideally it would change to Pressed, Down and Up. This would be a breaking change, but easy to correct in user applications.
The text was updated successfully, but these errors were encountered:
Glutin currently supports key press events and key release events. But (on Windows at least), key press events correspond to the virtual key presses that the OS does, including the repeated presses that occur when you hold the key down. I would really like to be able to get actual physical key down events as well, and distinguish between "presses" and key down events. At the moment, you can get more key press events than release events due to press repetition. I need this distinction for integration with the Chromium Embedded Framework, which has three types of key event - up, down and press.
The
ElementState
enum currently containsPressed
andReleased
. Ideally it would change toPressed
,Down
andUp
. This would be a breaking change, but easy to correct in user applications.The text was updated successfully, but these errors were encountered: