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
{{ message }}
This repository has been archived by the owner on Jul 19, 2023. It is now read-only.
First off, I absolutely love Scenic! Thanks so much for taking the time to create it, it is incredible.
I was wondering if you'd be open to supporting "keyboard state queries" in Scenic. It'd be useful for games that need to know the input state immediately. GLFW's key events are not as useful for real-time-y stuff, since they have "press", "repeat", and "release" phases that don't report back immediately.
How "immediate" do you need the response? In order to query glfw, the Elixir side of the driver needs to query the port, which then needs to act on it, and send another message back to the BEAM process.
Hmm, I'd like for it to complete within 1/60 of a second (so a frame). I was thinking of calling it here.
This may be wrong, but it seems like glfwGetKey will be fast, and the communication between Elixir and C is the questionable part. Do you think the Elixir-to-C communication will complete in time?
Hey Boyd,
First off, I absolutely love Scenic! Thanks so much for taking the time to create it, it is incredible.
I was wondering if you'd be open to supporting "keyboard state queries" in Scenic. It'd be useful for games that need to know the input state immediately. GLFW's key events are not as useful for real-time-y stuff, since they have "press", "repeat", and "release" phases that don't report back immediately.
Here's the part in the GLFW docs that describe the GLFW function we want: http://www.glfw.org/docs/latest/input_guide.html#input_key
What are your thoughts? 🙂
The text was updated successfully, but these errors were encountered: