You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Handling of the joystick, which was previously handled in the Activity;
=== After removal, only the surfaceView that currently has focus can handle events in multiple windows. Will this meet the expectations of developers?
Passing of Activity lifecycle, managing the native lifecycle (library load & unload)
=== After removal, will there be any issues with the android_native_app_glue lifecycle and event dispatching, as well as thread forwarding?
After removing GameActivity, can the corresponding code in GameActivity.cpp be retained, and is it necessary to retain it?
Game activity is a heavy sdk, we should re-consider to use it or not.
The text was updated successfully, but these errors were encountered: