- Deleted `DriverResolver`
- Moved and streamlined driver path extraction logic into `CustomSettingsHandler`.
- Improved string resource usage and ensured consistent formatting across dialogs.
* Introduced Toast messages across `CustomSettingsHandler`, `DriverResolver`, and `EmulationFragment` to improve user interaction and feedback for key operations.
* Enhanced error handling and confirmation dialogs, including options to launch with default settings when custom settings fail.
* Moved custom settings logic from `onCreate` to `handleEmuReadyIntent` for better readability.
* Added `showLaunchConfirmationDialog` to confirm game launch with or without custom settings.
* Updated `CustomSettingsHandler.findGameByTitleId` to show user feedback via `Toast`.
* Ensured improved separation of concerns and reusable methods.
* src/android/app/src/main/AndroidManifest.xml: Set targetApi to 33 and
enable onBackInvokedCallback to support the Android 13 predictive back gesture.
Also, add the tools namespace.
This commit introduces the ability to launch games with custom configurations supplied via an Android intent. This allows external applications to provide specific settings for a game at launch time.
Key changes include:
* **`CustomSettingsHandler.kt`**: A new class responsible for:
* Processing incoming intents with custom settings.
* Finding the target game in the user's library by its title ID.
* Writing the custom settings to a per-game INI file (`config/custom/<title_id>.ini`).
* Handling potential conflicts if a custom configuration already exists, prompting the user to overwrite or cancel.
* Integrating with `DriverResolver` to check for and handle required GPU drivers specified in the custom settings.
* Initializing the native per-game configuration.
* **`DriverResolver.kt`**: A new utility class for managing GPU drivers specified in custom settings:
* Extracts the driver path from the custom settings INI content.
* Checks if the required driver exists locally.
* If not found locally, searches for the driver in predefined GitHub repositories (Mr. Purple Turnip, GameHub Adreno 8xx, KIMCHI Turnip, Weab-Chan Freedreno).
* Prompts the user to download and install the missing driver if found online.
* Handles automatic download and installation of drivers using `DriverViewModel`.
* Notifies the user if a required driver cannot be found or installed.
* **`AndroidManifest.xml`**:
* Added a new intent filter for the action `dev.eden.eden_emulator.LAUNCH_WITH_CUSTOM_CONFIG` to `EmulationActivity`. This allows the app to respond to custom settings intents.
* **`EmulationFragment.kt`**:
* Modified `onCreate` to detect and handle the new custom settings intent.
* If a custom settings intent is received:
* It uses `CustomSettingsHandler.applyCustomSettingsWithDriverCheck` to process the settings asynchronously. This allows for driver checks and user interaction (e.g., overwrite confirmation, driver installation).
* Displays appropriate error messages via `Toast` if custom settings processing fails (e.g., game not found, driver issues).
* The game is then launched with the applied custom settings.
* If a regular file intent or navigation arguments are used, the existing logic for loading game configurations (including custom per-game configs) is retained.
* Ensures that per-game configurations are correctly loaded or unloaded based on how the game is launched.
* Introduced Toast messages across `CustomSettingsHandler`, `DriverResolver`, and `EmulationFragment` to improve user interaction and feedback for key operations.
* Enhanced error handling and confirmation dialogs, including options to launch with default settings when custom settings fail.
* Moved custom settings logic from `onCreate` to `handleEmuReadyIntent` for better readability.
* Added `showLaunchConfirmationDialog` to confirm game launch with or without custom settings.
* Updated `CustomSettingsHandler.findGameByTitleId` to show user feedback via `Toast`.
* Ensured improved separation of concerns and reusable methods.
* src/android/app/src/main/AndroidManifest.xml: Set targetApi to 33 and
enable onBackInvokedCallback to support the Android 13 predictive back gesture.
Also, add the tools namespace.
This commit introduces the ability to launch games with custom configurations supplied via an Android intent. This allows external applications to provide specific settings for a game at launch time.
Key changes include:
* **`CustomSettingsHandler.kt`**: A new class responsible for:
* Processing incoming intents with custom settings.
* Finding the target game in the user's library by its title ID.
* Writing the custom settings to a per-game INI file (`config/custom/<title_id>.ini`).
* Handling potential conflicts if a custom configuration already exists, prompting the user to overwrite or cancel.
* Integrating with `DriverResolver` to check for and handle required GPU drivers specified in the custom settings.
* Initializing the native per-game configuration.
* **`DriverResolver.kt`**: A new utility class for managing GPU drivers specified in custom settings:
* Extracts the driver path from the custom settings INI content.
* Checks if the required driver exists locally.
* If not found locally, searches for the driver in predefined GitHub repositories (Mr. Purple Turnip, GameHub Adreno 8xx, KIMCHI Turnip, Weab-Chan Freedreno).
* Prompts the user to download and install the missing driver if found online.
* Handles automatic download and installation of drivers using `DriverViewModel`.
* Notifies the user if a required driver cannot be found or installed.
* **`AndroidManifest.xml`**:
* Added a new intent filter for the action `dev.eden.eden_emulator.LAUNCH_WITH_CUSTOM_CONFIG` to `EmulationActivity`. This allows the app to respond to custom settings intents.
* **`EmulationFragment.kt`**:
* Modified `onCreate` to detect and handle the new custom settings intent.
* If a custom settings intent is received:
* It uses `CustomSettingsHandler.applyCustomSettingsWithDriverCheck` to process the settings asynchronously. This allows for driver checks and user interaction (e.g., overwrite confirmation, driver installation).
* Displays appropriate error messages via `Toast` if custom settings processing fails (e.g., game not found, driver issues).
* The game is then launched with the applied custom settings.
* If a regular file intent or navigation arguments are used, the existing logic for loading game configurations (including custom per-game configs) is retained.
* Ensures that per-game configurations are correctly loaded or unloaded based on how the game is launched.
