workshopsoft/ludic
2
0
Fork 0
Code Issues Pull requests Projects Releases 26 Packages Wiki Activity Actions

chore(release): v0.16.2
All checks were successful
bootstrap / cfree-fixpoint (push) Successful in 33s
Details
ci / build-and-test (push) Successful in 3m32s
Details
commit-lint / conventional-commits (push) Successful in 5s
Details
docs / build-and-deploy (push) Successful in 41s
Details
release / publish (push) Successful in 3m22s
Details

Browse source
This commit is contained in:
Orkun ÇAKILKAYA 2026-09-15 23:27:04 +03:00
parent 9a43b14f80
commit 132deac5bc
3 changed files with 19 additions and 17 deletions
Download patch file Download diff file Expand all files Collapse all files

16
changes/physical-keys.md
View file

@ -1,16 +0,0 @@
bump: patch
type: fix
**Keys are physical positions on Windows and macOS, whatever the layout** - `Input.key_down('w')`
is the key above S on every keyboard.
- **Windows** keyed the held set by the character the active layout gave a virtual key, so
a game's WASD belonged to whatever the layout put there: on AZERTY W and A were other
keys, and with an input method on (Chinese, Japanese, Korean) every letter arrived as
VK_PROCESSKEY and no letter key worked at all. The typing block is now read from the
scancode; the arrows, the numpad and the F-keys still go by virtual key, and the frame
key (`Input.key`, typing) keeps the layout's character.
- **macOS** did the same through `charactersIgnoringModifiers`; it now reads `keyCode`.
- **`Input.key_label(key)`** names a key for the player in their own layout - `'w'` shows
as "W" on QWERTY and "Z" on AZERTY - so a game that shows its bindings never shows a
key the player cannot find. Windows reads the layout; headless, macOS and the browser
give the US character.