vasya novikov

Hi @bbosen, thanks for the reply and for the explanation! Given what you say, would it be an idea to do exactly what the AppImage format asks: use relative paths? E.g. the relative path ../share/file.txt to /usr/bin/lac is /usr/share/file.txt, the relative path to /home/user/bin/lac is /home/user/share/file.txt, and so forth. That's the typical approach for relative handling of absolute paths if I understand it correctly. This way, you'd be able to run the same binary lac in however way you want,...

Currently, LAC's behavior depends on how it is started: lac or /usr/bin/lac or otherwise. In case of /usr/bin/lac started from the home directory, it will fail at startup, with an error description that might not be immediately obvious to new users (it wasn't understandable to me): Info: Dirs::Dirs() Function entry: Info: Dirs::Dirs() myfile = Info: .//LAC Fatal: Binary file has no context to the data files. Are you attempting to run LAC without first running our install.sh script? Please consult...

Currently, LAC's behavior depends on how it is started: lac or /usr/bin/lac or otherwise. In case of /usr/bin/lac started from the home directory, it will fail at startup, with an error description that might not be immediately obvious to new users (it wasn't understandable to me): Info: Dirs::Dirs() Function entry: Info: Dirs::Dirs() myfile = Info: .//LAC Fatal: Binary file has no context to the data files. Are you attempting to run LAC without first running our install.sh script? Please consult...

Currently, LAC's behavior depends on how it is started: lac or /usr/bin/lac or otherwise. In case of /usr/bin/lac started from the home directory, it will generally not run, with an error description that might not be immediately obvious to new users (it wasn't understandable to me): Info: Dirs::Dirs() Function entry: Info: Dirs::Dirs() myfile = Info: .//LAC Fatal: Binary file has no context to the data files. Are you attempting to run LAC without first running our install.sh script? Please consult...

I'd be curious to look.:)

Not that I really play freecol in the last months, but what's the commit hash for the fix? Does sourceforge has some nice trick to push a commit name "... fix SF-3114", and it will understand that the issue is fixed once the branch is merged (or right away if committed to master)?

@Mike, unfortunately, I don't play FreeCol that active anymore, so I guess we can mark the issue as fixed, and restore or raise a new issue if something will come up. // Exhaused early because winning at "maximum" difficulty was too easy, yet contaned many similar easy actions. Dunno how it would be with multiplayer, if it was alive. Sorry, anyway, I hope the project will live.

Well, I know for a fact that setting this property as first line of main() works. So we just need to find the right place for the code. I think I've gotta do it, because I'm the one that can observe different behavior. ( Though I still wonder what happens if you set this on Windows: https://sourceforge.net/p/freecol/bugs/3102/#e5b5/5f89 ) I'll do it a bit later.