Ziz
Advanced Member
- Joined
- Jan 15, 2006
- Messages
- 3,583
That is developer stuff. Developer don't care so much about the ergonomics as users do. I don't care if I have to define the buttons this way:I mentioned this too. My gamepads have numbers on the buttons and I never had problems with this, you just have to take care that the numbers match the input numeration in the driver.Another thing you didn't explain: Why not just using numbers?
(1) (4)
(2) (5)
(3) (6)I don't see any disadvantage. Nobody would tell you "Press button 1" or "Press (1)", if the person would mean the KEY 1 on the keyboard. In this case obviously the game button (1) is meant. Furthermore none of the emulated consoles uses numbers, so it isn't confusing anymore, that A is X, X is Y and B is actually A on this device.
#define BUTTON_1 12
#define BUTTON_2 14
#define BUTTON_3 16
#define BUTTON_4 13
#define BUTTON_5 15
#define BUTTON_6 17
However the pyra will probably use some keyboard keys again. So (1) will be page down, (2) page up, etc, so this doesn't matter at all.In my opinion IF we choose a ARM SOC, we should try to use a similar layout as for the pandora.