feat(desktop): log the keyboard map on startup - #822
Open
nborodikhin wants to merge 1 commit into
Open
Conversation
Name the desktop scancode constants after their SDL_SCANCODE_* values instead of raw numbers, and log the button-to-key map from PLAT_initInput() so a desktop build says which keys it answers to.
nborodikhin
marked this pull request as ready for review
August 23, 2026 20:42
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
On the dev-oriented desktop build keyboard key are mapped to the device buttons, but the mapping is not very clear.
This PR prints out key mapping every time an binary invoked
PAD_init()to remind developer of the mapping.Change
platform.c: addlogKeyMap(), call it fromPLAT_initInput()platform.h:CODE_*constants now use human-readableSDL_SCANCODE_*constantsTesting