konsumer / konsumer/web-zen-dev
input: mouse
Open
- Dominant language
- C
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
I think it should be mapped to canvas mouse events (the same canvas used for framebuffer?) I think it should go in `/dev/input/mice` or `/dev/input/eventX`
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing how the project exposes framebuffer/canvas input and review the `/dev/input/mice` and `/dev/input/eventX` options mentioned in the issue. Define which mouse events should reach the canvas and document a concrete completion criterion for WASI games, since no files or tests are identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, wasm
- Domain
- game-dev, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100