bspinner / amiberry-android Goto Github PK

Is your feature request related to a problem? Please describe.
As a user I want to use the emulator on the go without a hardware mouse. So I want to use touch movements on my screen for cursor movements in workbench etc.

Describe the solution you'd like

Expected behavior

1. Cursor moves relative to touch input
2. Left mouse button can be pressed by single press
3. Right mouse button can be pressed by single press with two fingers

Describe alternatives you've considered

1. Right and middle mouse button could be emulated via buttons in onscreen controller (maybe hidden in "meta menu")

As of now, Assets have to be manually copied from the amiberry repo into the app's assets directroy.
It be nice to have this done automatically by gradle as part of the build process.

Benefits:

• less manual work
• updates done to the amiberry repo are included automatically

The android app needs some graphics, like

• App icon
• Startup screen

As of now, the write_log redirection to SDL_Log leads to crashes and will be removed soon (writing to logfile works now).
Logcat output might be interesting in the future for proper crashlogs from users.

The onscreen controller isn't displayed even when activated.

edit: So, I started working on this.

• Show OnScreen Controller (OSC) with D-Pad and one Fire Button
• Enable user to enable/disable osc via Settings menu
  • Enable user to add additional fire buttons (up to 4)
• Enable user to show native keyboard for text input
• Add smaller button which shows additional "meta" buttons:
  • show Amiberry GUI, like F12 (later: stop emulation and go back to Library)
  • later: enable/disable touches for mouse input

Currently necessary files aren't deployed with the app.
E.g. the data folder with graphics.

Those could be delivered as assets and extracted in the app's external directory. So they can be accessed by NDK and modified by the users via file system.
Alternatively there's https://developer.android.com/ndk/reference/group/asset .

Amiberry currently makes assumptions about paths on the filesytem.
This clashes with how Android handles this. An initial solution to this could be a static function which prefixes given paths by a appropiate root path.

The app crashes when the user uses the quit button in amiberry and tries to restart it afterwards via proceed button in Android UI.

As a user I want to interact with the Amiberry GUI as long as there's no Android GUI,
so I am able to configure the emulation.