Hajime Hoshi b7dd45c0e4 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:28:48 +09:00
..
_files	internal/gamepad: ignore the very first MotionEvent with 0 value for Android	2024-03-21 22:28:48 +09:00
gobind.go	cmd/ebitenmobile: use go:embed (#2435)	2022-11-04 17:20:21 +09:00
gomobile.go	all: use github.com/ebitengine/gomobile instead of golang.org/x/mobile	2024-02-24 22:07:27 +09:00
main_test.go	cmd/ebitenmobile: check the Java package before an execution	2024-01-28 15:52:16 +09:00
main.go	all: use github.com/ebitengine/gomobile instead of golang.org/x/mobile	2024-02-24 22:07:27 +09:00