feat: add clickable console controls - #28
Merged
Merged
Conversation
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.
The console's left, right, and Commit buttons now work alongside keyboard controls, using aligned pressed-state image overlays. Start/On turns an active game off and starts a fresh round when off or dead.
The buttons live in
ui/controls.tsx, movement shares one bounded handler, and movement clears the firing animation for both keyboard and pointer input. Button assets use numbered names and eight PNGs are losslessly optimized, saving 22,355 bytes while preserving decoded pixels and color profiles.Validation:
npm run checkandnpm run buildpassed. Browser checks verified button positioning, movement, and firing. PNG dimensions, decoded RGBA pixels, and color profiles were compared before replacement. The build retains the existing large-chunk warning.