We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This bug seems to be a glfw bug, it apparently was fixed on glfw3.3 but the latest golang port is 3.2.
glfw/glfw#747
I might try to do something with the pooling rate or do something more hacky, something like a "debounce"
The text was updated successfully, but these errors were encountered:
glfw3.3 is right around the corner. I'll wait for a few more days to see if will be fixed on glfw3.3 go-gl/glfw#256
Sorry, something went wrong.
Just figured out that the key event also was fired on keyUp. Fixed on commit 18cfeb8
No branches or pull requests
This bug seems to be a glfw bug, it apparently was fixed on glfw3.3 but the latest golang port is 3.2.
glfw/glfw#747
I might try to do something with the pooling rate or do something more hacky, something like a "debounce"
The text was updated successfully, but these errors were encountered: