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
I've developed a couple of apps now that can load from a hexpansion EEPROM, and they auto-run on insertion.
If the app displays a UI, it can foreground itself and the user can interact with it. If the app is then minimised, there is no way of returning to the app even though it is still running.
Ideally when an app is launched from a hexpansion EEPROM it should be added to the launcher menu along with the other installed apps (maybe with an identifier to show it's a hexpansion app, or within a "Hexpansions" submenu) so that the user can re-open it when minimised.
Maybe this could be done by exposing part of the Launcher API to the app, so the app can add itself into the menu. That way hexpansions with no UI or that only require a background service won't get added.
The text was updated successfully, but these errors were encountered:
I've developed a couple of apps now that can load from a hexpansion EEPROM, and they auto-run on insertion.
If the app displays a UI, it can foreground itself and the user can interact with it. If the app is then minimised, there is no way of returning to the app even though it is still running.
Ideally when an app is launched from a hexpansion EEPROM it should be added to the launcher menu along with the other installed apps (maybe with an identifier to show it's a hexpansion app, or within a "Hexpansions" submenu) so that the user can re-open it when minimised.
Maybe this could be done by exposing part of the Launcher API to the app, so the app can add itself into the menu. That way hexpansions with no UI or that only require a background service won't get added.
The text was updated successfully, but these errors were encountered: