fixed reversed X/Y buttons in drastic-trngaje on the brick#729
Merged
xonglebongle merged 2 commits intoJun 24, 2026
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 TrimUI Brick's X and Y buttons are reversed in
drastic-trngaje. Both their in-game functions (e.g. pressing the hardware X button presses the Y button in-game) and their in-emulator functions (e.g. pressing Menu + Y opened the emulator menu, instead of the intended Menu + X) are reversed.This fix simply swaps all references to the hardware X/Y buttons in the device-specific
drastic.cfg, restoring proper behavior. This fix was tested in muOS's current version of the core as well as with a manually-updated version from https://github.com/trngaje/advanced_drastic/releases/tag/libadvdrastic . X/Y function was confirmed using a test ROM as well as the emulator menu hotkey.Possible concerns:
controls_b[CONTROL_INDEX_UI_BACK]andcontrols_b[CONTROL_INDEX_UI_PAGE_UP]even work? It kinda seems like they don't, for me. I swapped them anyway.