Design & develop keyboard input API for Ludus #45

New Issue

scott · 2025-06-28T22:17:13Z

scott commented

2025-06-28 22:17:13 +00:00

Model this after p5's strategy.

We'll have three functions that are all (:keyword) -> :bool: key_down?, key_pressed?, and key_released?.

This should be easy enough!

Model this after p5's strategy. We'll have three functions that are all `(:keyword) -> :bool`: `key_down?`, `key_pressed?`, and `key_released?`. This should be easy enough!

scott added the

feature

design

labels 2025-07-02 16:29:40 +00:00

scott added this to the Core: CC2 milestone 2025-07-02 17:15:25 +00:00

scott commented

2025-07-04 19:30:52 +00:00

This is the correct design!

scott commented

2025-07-06 05:43:40 +00:00

Done: we actually only have key_down?: the rest of what we need for now can be done with sleep timers: in place of a key_pressed? function, which would only return true once per io tick, we can devise a dead simple timer that just checks to see if a key is down at an interval. Cute!

Done: we actually only have `key_down?`: the rest of what we need for now can be done with sleep timers: in place of a `key_pressed?` function, which would only return `true` once per io tick, we can devise a dead simple timer that just checks to see if a key is down at an interval. Cute!

scott closed this issue

2025-07-06 05:43:40 +00:00

Sign in to join this conversation.