by Davin Church » November 11th, 2018, 12:37 pm
That's an interesting thought, though I don't ever tie files by relative path - I always specify them explicitly so I don't run into the problem you have.
Just FYI - I typically use a function I called CWD (Current Workspace Directory) which returns to me the path to the loaded workspace. I then use that path to reference files which I expect to find alongside the workspace itself. For exceptions to this, I can localize an "override" variable so that CWD returns the path of my choice and I can continue to use CWD everywhere without caring where it's really pointing. Of course, user-specified paths have to be stored and used in a variable, which I do in those cases. Virtually none of my code cares what the "current directory" is in any case - it could be getting set to random directories at random times and it wouldn't affect the application.