Xargon/ES-DE
1
0
Fork 0
mirror of https://github.com/RetroDECK/ES-DE.git synced 2024-11-21 13:45:38 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Documentation update.

Browse source
This commit is contained in:
Leon Styhre 2022-05-09 20:57:42 +02:00
parent 7b07ccb44d
commit 72d6f88a61
3 changed files with 11 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
CHANGELOG.md
View file

@ -156,6 +156,9 @@ v1.2 maintenance release.
### Bug fixes
* Chinese characters would sometimes not render correctly
* The "Jump to.." quick selector didn't work correctly with multi-byte Unicode characters
* (Linux) Flatpak directories were missing for user installations of the standalone emulators BlastEm, Play! and Snes9x
* (Windows) Fixed an issue where symlinking game media directories would crash the application
* (Windows) Scripts and links executed using cmd.exe could not contain the special characters &()^=;,
* (Windows) ROM directories could not be created in the root of a device such as D:\ or E:\

4
USERGUIDE-DEV.md
View file

@ -518,6 +518,8 @@ Therefore all bundled emulator configuration entries that support AppImages will
~/bin/
```
It's generally recommended to go for the ~/Applications/ directory, but depending on your Linux distribution this may or may not exist by default. If the directory doesn't exist, then just go ahead and create it. Keep in mind that Linux is case-sensitive so make sure to spell it with a capital A.
As AppImages often embed version information into the actual filename, the bundled configuration uses wildcards to locate the files, such as `rpcs3*.AppImage` which would match the filename `rpcs3-v0.0.19-13103-cc21d1b3_linux64.AppImage` for instance. Note that if multiple files match the wildcard pattern, the first file returned by the operating system will be selected.
This approach also works when using [AppImageLauncher](https://github.com/TheAssassin/AppImageLauncher) which is recommended as it properly integrates AppImages into the application menu and such. When first launching an AppImage with AppImageLauncher installed a question will be asked whether to integrate the application. If accepting this, the AppImage will be moved to the `~/Applications` directory and a hash will be added to the filename, like in this example:
@ -560,6 +562,8 @@ For these situations ES-DE looks for emulators in the same directories where it
~/bin/
```
It's generally recommended to go for the ~/Applications/ directory, but depending on your Linux distribution this may or may not exist by default. If the directory doesn't exist, then just go ahead and create it. Keep in mind that Linux is case-sensitive so make sure to spell it with a capital A.
So placing a manually downloaded emulator binary in either of these directories will make ES-DE able to locate it during game launch.
The following manually downloaded emulators are supported when using the bundled configuration:

4
USERGUIDE.md
View file

@ -516,6 +516,8 @@ As such all bundled emulator configuration entries that support AppImages will l
~/bin/
```
It's generally recommended to go for the ~/Applications/ directory, but depending on your Linux distribution this may or may not exist by default. If the directory doesn't exist, then just go ahead and create it. Keep in mind that Linux is case-sensitive so make sure to spell it with a capital A.
But even if the directory is known, another issue is that many AppImages contain version information in the filename, such as:
```
rpcs3-v0.0.19-13103-cc21d1b3_linux64.AppImage
@ -576,6 +578,8 @@ For these situations ES-DE looks for emulators in the same directories where it
~/bin/
```
It's generally recommended to go for the ~/Applications/ directory, but depending on your Linux distribution this may or may not exist by default. If the directory doesn't exist, then just go ahead and create it. Keep in mind that Linux is case-sensitive so make sure to spell it with a capital A.
So placing a manually downloaded emulator binary in either of these directories will make ES-DE able to locate it during game launch.
The following manually downloaded emulators are supported when using the bundled configuration: