diff options
| author | JosJuice <josjuice@gmail.com> | 2023-06-06 22:07:14 +0200 |
|---|---|---|
| committer | JosJuice <josjuice@gmail.com> | 2023-06-06 22:07:14 +0200 |
| commit | 71ac6ec23962a360e1f08abc3c7ff989ac8f1106 (patch) | |
| tree | 3390ecffdea00c07fcec2c01c7737d0fad52058c /Source/Core/Common/FileUtil.cpp | |
| parent | 5d40871dd458ccb289beabeb35a2eff4c4c5625e (diff) | |
InputCommon: Don't treat two analog inputs as a spurious trigger combo
I've received a report from an Android user with a gamepad (a "BSP-D3")
where one physical trigger is controlling two analog axes at the same
time. This was causing RemoveSpuriousTriggerCombinations to delete both
axes, which is clearly not a desireable outcome.
With this change, now the axis with the greatest smoothness is kept,
or both in case they have the same smoothness.
Diffstat (limited to 'Source/Core/Common/FileUtil.cpp')
0 files changed, 0 insertions, 0 deletions