Opened 2 years ago
Last modified 2 years ago
#13614 new defect
RISC OS Scumm 2.6.0 abuses user choices
| Reported by: | gerph | Owned by: | |
|---|---|---|---|
| Priority: | normal | Component: | Port: RISC OS |
| Version: | Keywords: | ||
| Cc: | Game: |
Description
Hiya,
The 2.6.0 stable version of ScummVM abuses the Choices directory for its debug output.
The line in question is in !ScummVM.!Run:
`
Set Alias$Run_ScummVM Run <Obey$Dir>.scummvm %%*0 ><Choices$Write>.ScummVM.stdout 2><Choices$Write>.ScummVM.stderr
`
Choices should be used for configuration information, not for diagnostics. If you have diagnostics you should write them to Scrap$Dir at the very least. Using <Choices$Write> would be akin to writing to /etc/scummvm/stderr on a unix system, or possibly $XDG_CONFIG/ScummVM/stderr which hopefully you can see makes the decision to use Choices$Write clearly wrong.
Note:
See TracTickets
for help on using tickets.
I'd prefer to leave this as is - RISC OS doesn't have a standardised location for storing log files, and keeping it alongside the configuration file and save files ensures that it can easily be found by the user in the event of a crash. This is consistent with the Windows port's behaviour, which writes the logs to the Application Data folder instead of to the system temporary folder.
Is there precedence for keeping log files in !Scrap? If there is, I might change my mind on this.