FOUR stupid issues with the PAD config UI

[MayImilae]

kirbypuff Wrote:Issue #3: The per-pad "Background Input" setting got broken in the latest dev builds. (it worked perfectly in older / stable builds)
---------------------------------------------------------------------------------------------------------------------------------------------------------------------
Steps to reproduce the issue:

- Enable "Background Input" for PAD1 only, then disable it for pads 2,3 and 4 and save the settings. Open the PAD UI. Now *ALL* 4 pads have background input enabled (!)
- Now disable "Background Input" for pads 2,3 and 4 (leave the PAD1 setting to "enabled"), save the settings and re-open the PAD UI. Background input gets dsabled for ALL 4 PADs (!)

It's a global setting: you change it in one, you change it in them all. It was intentionally changed to be like this to clean up some seriously messy code within the background input system, and it was kept in the original position because there was no better place to put it, and no one should be messing with background input for specific controllers like that anyway. Seriously, why were you? We didn't expect anyone to even notice it!

[RachelB]

It could be a convenient way to handle multiple controllers, where one is mapped to a keyboard, and the other is mapped to a controller. Background input is nice with a controller, but not so much with a keyboard that's used for other purposes too. Although, i admit, that's a pretty big stretch.