Adding X and Y Buttons as extra keys for L and R

[LodanZark]

Adding X and Y Buttons as extra keys for L and R which is very handy for certain games specially fighting and fast paced action alike street fighter alpha 3 and sonic battle

[andres-asm]

You can alter the mapping with core input remapping. In any case this
should be an option not a default behavior

On Tue, Apr 19, 2016, 9:19 AM LodanZark notifications@github.com wrote:

Adding X and Y Buttons as extra keys for L and R which is very handy for
certain games specially fighting and fast paced action alike street fighter

alpha 3 and sonic battle

You can view, comment on, or merge this pull request online at:

#40
Commit Summary

• Adding X and Y Buttons as extra keys for L and R

File Changes

• M libretro/libretro.cpp
  https://github.com/libretro/vba-next/pull/40/files#diff-0 (10)

Patch Links:

• https://github.com/libretro/vba-next/pull/40.patch
• https://github.com/libretro/vba-next/pull/40.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#40

[LodanZark]

There is no issues or whatsoever, this change already happened in lr-gpsp and there is no negative reports neither complaints, it's important preserve the L and R buttons in their default mapping in situations that requires press L+A or R+B alike metroid games, and some games are better using the X Y instead R L because the buttons are closer, I am not removing the traditional mapping, I am giving more options and bring the best from both worlds specially since buttons X and Y are not being used, plus would be a mess adding core input remapping for each different game.

[inactive123]

Alright, I dont see much wrong with this.

[inactive123]

Actually, thinking about it, it doesn't make much sense and having two conflicting L/R bound keys as input descriptors causes bad conflicts. So reverting this entirely.