Keyboard interaction should work #94

Open
opened 2025-07-09 22:31:41 +00:00 by scott · 1 comment
Owner

The basic mechanism for keyboard interaction should work much better than it does.

key_down? is sampled too many times per event loop to be useful: it's too many messages back and forth, and also weirdly not responsive.

I suspect this will require some kind of architectural change, like perhaps shared memory between JS and Rust, rather than message passing.

The basic mechanism for keyboard interaction should work much better than it does. `key_down?` is sampled too many times per event loop to be useful: it's too many messages back and forth, and also weirdly not responsive. I suspect this will require some kind of architectural change, like perhaps shared memory between JS and Rust, rather than message passing.
scott added the
bug
feature
design
labels 2025-07-09 22:33:29 +00:00
Author
Owner

Also, definitely related to #50: this will work much better once we're not drawing a bunch of teeny tiny sub-pixel lines to make paths.

Also, definitely related to #50: this will work much better once we're not drawing a bunch of teeny tiny sub-pixel lines to make paths.
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: twc/ludus#94
No description provided.