odd location for infolog

[zwzsg]

Now when I drop a startscript over Spring.exe, it makes the infolog, the ArchiveCacheV7.lua and the ext.txt at: C:\Program Files\Fichiers communs\System\Mapi\1036\NT\infolog.txt (Oh and also demos, screenshots, AI, widget config...

[imbaczek]

fix one thing, two more show up... this is because the working directory gets set to something strange, i guess. the problem is, sometimes it's a good thing to have and sometimes not. proposed solution:
- don't use the working directory when running demos
- ditto for unitsync
- provide an option for unitsync to use the working directory
- make it possible for the working directory to be scanned in read only mode in both the engine and unitsync

unitsync will require a new api call or two, i guess.

[Tobi]

Working directory may be anything, practically, should never rely on it without having set it explicitly first. Wouldn't it be better to use spring.exe / unitsync.dll location? (Pretty sure there must be a GetModuleFileName or something that returns the DLL path instead of executable path on Windows...)

[thesleepless]

how about always putting it in the user's writable spring directory?
it's annoying having infologs all over the place.

[imbaczek]

Wouldn't it be better to use spring.exe / unitsync.dll location?

it would, but e.g. bibim wants cwd support in unitsync for spads. don't know if SPRING_DATADIR env var works for him.

[Tobi]

IMO that should be done using the environment variable yeah, as far as I've seen all these hardcoded datadir paths have caused more problems then what they have solved.

Maybe we should add a way to remove paths, instead of only having support to add paths

[Pxtl]

Why are there so many folders being used? I thought there would be 2 - the static Program Files folder, and the Userland folder. Why are there so many others?

[Tobi]

AFAIK the only other one is the cwd