Yep, that one.Nach wrote:The second is where you understand it, but you scratch your head wondering why.
Bug: Screenshots do not save to proper folder
Moderator: ZSNES Mods
-
creaothceann
- Seen it all
- Posts: 2302
- Joined: Mon Jan 03, 2005 5:04 pm
- Location: Germany
- Contact:
vSNES | Delphi 10 BPLs
bsnes launcher with recent files list
bsnes launcher with recent files list
yes, zsnes changes the active directory, it has to for many reasons.
for example when you load your roms it does this to get a romlist, or to check which save state files you have, etc.
The user won't notice unless he's in dos and ctrl-breaks (which probably doesn't work anyway)
for example when you load your roms it does this to get a romlist, or to check which save state files you have, etc.
The user won't notice unless he's in dos and ctrl-breaks (which probably doesn't work anyway)
To truly own, you must own at all games.
rlbond and Nach seem to be going back and forth on questioning what relative paths should be relative to.
Personally, I see absolutely no use in having relative paths to the current working directory (regardless of what method zsnes uses to determine that). rlbond's argument is for paths relative to the zsnes executable, which seems to be of far more actual use.
With relative paths established using rlbond's scheme, you can setup your zsnes directory however you like, and then move the whole directory anywhere. This cannot be done with absolute paths, clearly.
Under what circumstances would it be favorable and/or useful to have relative paths dependent on an arbitrary location like the CWD? Consider also the fact that most Windows users have no significant knowledge of CLI or its terminology and inner workings. Even on unix-likes, there is no global CWD; only one relative to the current shell. It is up to the running application to use the path it is launched from in the way most beneficial to the majority of users.
Personally, I see absolutely no use in having relative paths to the current working directory (regardless of what method zsnes uses to determine that). rlbond's argument is for paths relative to the zsnes executable, which seems to be of far more actual use.
With relative paths established using rlbond's scheme, you can setup your zsnes directory however you like, and then move the whole directory anywhere. This cannot be done with absolute paths, clearly.
Under what circumstances would it be favorable and/or useful to have relative paths dependent on an arbitrary location like the CWD? Consider also the fact that most Windows users have no significant knowledge of CLI or its terminology and inner workings. Even on unix-likes, there is no global CWD; only one relative to the current shell. It is up to the running application to use the path it is launched from in the way most beneficial to the majority of users.