The user shouldn't need to access config files, because the app should have an options menu.SteveM said:I used save states as an example, but the same is true for configuration files or other data read or written by an app. I guess we'll have every app open a file picker when it starts so you can specify where your configuration file is? Or maybe the user could specify paths in some kind of file under appdata - oh, wait...
For the same reason you shouldn't put roms in there, you might want to access them from more than one emulator.
I know there tend to be incompatible savestate formats, but at least SRAM saves are pretty standard.
You could equally well say documents are "data pertaining to Abiword", but no one would suggest you store them all in appdata.
EDIT: As you say, the discussion of whether pandora/ is hidden or not is irrelevant.
But the discussion about what should and should not go in appdata is important.
Basically I want to avoid, for example, as happened in the past, users having to copy bios files into exactly the right place before something will work.
This creates dozens of confused users, and the zenity frontend to avoid that is a few lines of script.
Last edited by a moderator: