Hajime Hoshi e2f26b9dac internal/gamepad: ignore the very first MotionEvent with 0 value for Android ... On Android, MotionEvent with 0 values might come for axes when connecting a gamepad, even though a user didn't touch any axes. This is problematic especially for tirgger axes, where the default value should be -1. This change fixes the issue by adding a new state `axesReady` to check if an axis is really touched or not. If an axis is not touched yet, a button value for a standard (trigger) button always returns 0. This change also removes an old hack to initialize axis values for triggers. Closes #2598		2024-03-21 22:48:33 +09:00
..
ebitenmobile	internal/gamepad: ignore the very first MotionEvent with 0 value for Android	2024-03-21 22:48:33 +09:00