It looks as though for now, we can’t edit the controls for Drastic.
I’ve tried to use xmodmap to make a custom entry as follows:
! -*- coding: utf-8 -*-
! 2020-03-10
! set Gameshell keys to Pandora Drastic Mapping
! keycode 86 = SPACE 32
! keycode 9 = PANDORA 147
! keycode 45 = A 278
! keycode 44 = B 279
! keycode 30 = X 280
! keycode 31 = Y 281
! keycode 29 = L 303
! keycode 32 = R 305
! keycode 65 = Select 306
! keycode 36 = Start 308
keycode 86 = 0020
keycode 9 = 0093
keycode 45 = 0116
keycode 44 = 0117
keycode 30 = 0118
keycode 31 = 0119
keycode 29 = 012f
keycode 32 = 0131
keycode 65 = 0132
keycode 36 = 0134
and incorporating a “kill switch” using xbindkeys:
# RETURN KEYS TO NORMAL
"xmodmap ~/apps/emulators/drastic/.xmodmap_original && xbindkeys --defaults > ~/.xbindkeysrc && killall xbindkeys && killall drastic"
Escape
Theoretically, it should work however I don’t think I’ve gotten the correct hex values of what the expected output from Drastic is meant to be. From the looks of things, it was written for the Pandora console. I can find a table of the suspected keycodes correlating to each input key, however I need either the keysym or the hex code for each button to work with xmodmap. The mapping I have currently made was one I came up with, searching high and low for whatever I could re: how the Pandora is mapped. In a nutshell, it sounds like no one in the Pandora community can come to any consensus as to what the mappings actually are.
Does anyone possibly own a pandora, and could they possibly run xev
and show the printouts for each of the Pandora’s “ABXYLR+START+SELECT+HOME” inputs?
I have also reached out and contacted the author, and asked politely if he could possibly provide the source code to allow us to customise it to the Gameshell’s control scheme.
For now, we may be able to get it working.