Files
android-activity/examples/agdk-winit-wgpu
Robert Bragg 7cdb77eca4 Let applications report if they handled input events
The callback given to `AndroidApp::input_events()` is now expected to return
`InputStatus::Handled` or `InputStatus::Unhandled`.

When running with NativeActivity then if we know an input event hasn't been
handled we can notify the InputQueue which may result in fallback
handling.

Although the status is currently ignored with the GameActivity backend.

Since this is a breaking change that also affects the current Winit
backend this updates the winit based examples to stick with the 0.3
release of android-activity for now.

Fixes: #31
2022-09-20 00:14:38 +01:00
..
2022-08-14 11:02:22 +01:00
2022-08-24 21:23:29 +01:00
2022-07-03 23:34:25 +01:00

This tests using GameActivity with winit and wgpu.

This is based on a re-worked winit backend here: https://github.com/rib/winit/tree/android-activity

Although it would have been possible to handle the suspend/resume lifecycle events with a simpler approach of destroying and recreating all graphics state, this tries to represent how lifecycle events could be handled in more complex applications, such as within Bevy.

Considering that lifecycle events aren't supported consistently on desktop platforms this test also aims to build and run on desktop - for the sake of testing how more complex applications (that need to be portable) can work. (enable "desktop" feature to build binary)

export ANDROID_NDK_HOME="path/to/ndk"
export ANDROID_HOME="path/to/sdk"

rustup target add aarch64-linux-android
cargo install cargo-ndk

cargo ndk -t arm64-v8a -o app/src/main/jniLibs/  build
./gradlew build
./gradlew installDebug
adb shell am start -n co.realfit.agdkwinitwgpu/.MainActivity