Most programs with controller support allow for setting a button for each action you can do in the program. But mgalaxy only allows swapping buttons in terms of the default config.
Here's an example where it makes a difference:
up/down scrolls the game list while left/right pages.
I want to set it so left/right switches systems and I have some other buttons to page.
If I do that, then left/right navigation in menus doesn't work anymore. If I'm in the "exit yes/no" dialog, or the virtual keyboard of the search feature, left/right now do nothing and I have to press my other paging buttons to go left/right in the menu.
Controller mapping per-action
I don't follow (or understand) you!
If you set DPadLeft/DPadRight buttons to GoToPreviousEmulator/GoToNextEmulator action.
If you set (let's say) LeftTrigger to 'page up' and RightTrigger to 'page down'.
Those LeftTrigger/RightTrigger buttons will act as left/right direction buttons in all windows!!!
If you set DPadLeft/DPadRight buttons to GoToPreviousEmulator/GoToNextEmulator action.
If you set (let's say) LeftTrigger to 'page up' and RightTrigger to 'page down'.
Those LeftTrigger/RightTrigger buttons will act as left/right direction buttons in all windows!!!
Last edited by mgalaxy on Sat Nov 15, 2014 8:35 am, edited 1 time in total.
Yes, that's the problem. Say I map page up/down to right stick up and down. Navigating menus is still technically possible but very awkward.mgalaxy wrote: I don't follow (or understand) you!
If you set DPadLeft/DPadRight buttons to GoToPreviousEmulator/GoToNextEmulator action.
If you set (let's say) LeftTrigger to 'page up' and RightTrigger to 'page down'.
Those LeftTrigger/RightTrigger buttons will act as left/right direction buttons in all windows!!!
If I could separately map "menu up/down/left/right" actions it would solve the issue