diff options
| author | Maksim Gamarnik <MoNTE48@mail.ua> | 2016-05-14 23:35:56 +1000 |
|---|---|---|
| committer | Craig Robbins <kde.psych@gmail.com> | 2016-05-14 23:42:36 +1000 |
| commit | b906ed4e5902785ab6f15012666e344c98fabe14 (patch) | |
| tree | 886939eb69edccb0881255fd95ac51ece4b52da0 /fonts/lucida_sans_180.png | |
| parent | ec15e35ad7effe54d04c0d34ead3bc63d0e311f1 (diff) | |
| download | minetest-b906ed4e5902785ab6f15012666e344c98fabe14.tar.gz minetest-b906ed4e5902785ab6f15012666e344c98fabe14.tar.bz2 minetest-b906ed4e5902785ab6f15012666e344c98fabe14.zip | |
Fix locked hardware buttons on Android
Fixes #2122
Fixes #1454
Addendum (est31)
According from its docs in android_native_app_glue.h (from the NDK), the
onInputEvent should "Return 1 if you have handled the event, 0 for any
default dispatching". Before, we always returned 1, meaning we blocked
all hardware keys to be given to the OS.
This broke the volume keys and has caused #2122 and #1454.
Although it bases on lots of guesswork, it can probably safely be said that
CGUIEnvironment::postEventFromUser returns true if the event was handled,
and false if not. Therefore, set the status variable depending on what
postEventFromUser returned.
Diffstat (limited to 'fonts/lucida_sans_180.png')
0 files changed, 0 insertions, 0 deletions