From 6a6d9904dc3e7e970ee1c6a0ca90d0c1cccc25d3 Mon Sep 17 00:00:00 2001 From: Leon Styhre Date: Mon, 4 Mar 2024 23:49:43 +0100 Subject: [PATCH] Documentation update --- ANDROID-DEV.md | 34 +++++++++++++++++----------------- ANDROID.md | 34 +++++++++++++++++----------------- 2 files changed, 34 insertions(+), 34 deletions(-) diff --git a/ANDROID-DEV.md b/ANDROID-DEV.md index 088450060..86df32043 100644 --- a/ANDROID-DEV.md +++ b/ANDROID-DEV.md @@ -93,7 +93,7 @@ The way ES-DE works is that you have a defined ROMs directory which corresponds ``` -Here the path tag is using the %ROMPATH% variable to keep it relative to the base ROMs directory as selected via the onboarding configurator when you first installed ES-DE. If you relocate your ROMs directory to a different storage device, or to another device altogether or if you synchronize your games across Android and Linux, macOS or Windows then everything will still work correctly. +Here the path tag is using the %ROMPATH% variable to keep it relative to the base ROMs directory as selected via the onboarding configurator when you first installed ES-DE. If you relocate your ROMs directory to a different storage device, or copy it to another device altogether or if you synchronize your games across Android and Linux, macOS or Windows then everything will still work correctly. Similarly custom collection files contain the %ROMPATH% variable too, such as this: ``` @@ -116,14 +116,14 @@ Here's an example of a custom es_systems.xml file that relocates the samcoupe sy - samcoupe - MGT SAM Coupé - /storage/719F-3A7F/ROMs/samcoupe - .dsk .DSK .mgt .MGT .sad .SAD .sbt .SBT .7z .7Z .zip .ZIP - %EMULATOR_SPECCY% %ACTION%=android.intent.action.VIEW %DATA%=%ROMSAF% - samcoupe - samcoupe - + samcoupe + MGT SAM Coupé + /storage/719F-3A7F/ROMs/samcoupe + .dsk .DSK .mgt .MGT .sad .SAD .sbt .SBT .7z .7Z .zip .ZIP + %EMULATOR_SPECCY% %ACTION%=android.intent.action.VIEW %DATA%=%ROMSAF% + samcoupe + samcoupe + ``` @@ -137,14 +137,14 @@ Here's again an example for the samcoupe system: - samcoupe - MGT SAM Coupé - /storage/emulated/0/ROMs/samcoupe - .dsk .DSK .mgt .MGT .sad .SAD .sbt .SBT .7z .7Z .zip .ZIP - %EMULATOR_SPECCY% %ACTION%=android.intent.action.VIEW %DATA%=%ROMSAF% - samcoupe - samcoupe - + samcoupe + MGT SAM Coupé + /storage/emulated/0/ROMs/samcoupe + .dsk .DSK .mgt .MGT .sad .SAD .sbt .SBT .7z .7Z .zip .ZIP + %EMULATOR_SPECCY% %ACTION%=android.intent.action.VIEW %DATA%=%ROMSAF% + samcoupe + samcoupe + ``` diff --git a/ANDROID.md b/ANDROID.md index 5730044a0..864b31722 100644 --- a/ANDROID.md +++ b/ANDROID.md @@ -93,7 +93,7 @@ The way ES-DE works is that you have a defined ROMs directory which corresponds ``` -Here the path tag is using the %ROMPATH% variable to keep it relative to the base ROMs directory as selected via the onboarding configurator when you first installed ES-DE. If you relocate your ROMs directory to a different storage device, or to another device altogether or if you synchronize your games across Android and Linux, macOS or Windows then everything will still work correctly. +Here the path tag is using the %ROMPATH% variable to keep it relative to the base ROMs directory as selected via the onboarding configurator when you first installed ES-DE. If you relocate your ROMs directory to a different storage device, or copy it to another device altogether or if you synchronize your games across Android and Linux, macOS or Windows then everything will still work correctly. Similarly custom collection files contain the %ROMPATH% variable too, such as this: ``` @@ -116,14 +116,14 @@ Here's an example of a custom es_systems.xml file that relocates the samcoupe sy - samcoupe - MGT SAM Coupé - /storage/719F-3A7F/ROMs/samcoupe - .dsk .DSK .mgt .MGT .sad .SAD .sbt .SBT .7z .7Z .zip .ZIP - %EMULATOR_SPECCY% %ACTION%=android.intent.action.VIEW %DATA%=%ROMSAF% - samcoupe - samcoupe - + samcoupe + MGT SAM Coupé + /storage/719F-3A7F/ROMs/samcoupe + .dsk .DSK .mgt .MGT .sad .SAD .sbt .SBT .7z .7Z .zip .ZIP + %EMULATOR_SPECCY% %ACTION%=android.intent.action.VIEW %DATA%=%ROMSAF% + samcoupe + samcoupe + ``` @@ -137,14 +137,14 @@ Here's again an example for the samcoupe system: - samcoupe - MGT SAM Coupé - /storage/emulated/0/ROMs/samcoupe - .dsk .DSK .mgt .MGT .sad .SAD .sbt .SBT .7z .7Z .zip .ZIP - %EMULATOR_SPECCY% %ACTION%=android.intent.action.VIEW %DATA%=%ROMSAF% - samcoupe - samcoupe - + samcoupe + MGT SAM Coupé + /storage/emulated/0/ROMs/samcoupe + .dsk .DSK .mgt .MGT .sad .SAD .sbt .SBT .7z .7Z .zip .ZIP + %EMULATOR_SPECCY% %ACTION%=android.intent.action.VIEW %DATA%=%ROMSAF% + samcoupe + samcoupe + ```