There are currently still a few things that seem to save with full paths rather than relative ones. Trigger sounds, external script file, basically anything that comes from a browse dialog. We've been getting a lot of requests lately about transferring MUSHclient with settings intact from one computer to another, and this is getting in the way. What do you think about making sure that all browse dialogues convert the result to a relative path for anything inside the MUSHclient directory?
relative path saving for all browse locations within the main directory
Posted by Fiendish on Tue 09 Jan 2018 12:41 AM — 3 posts, 12,017 views.
I am wary of the file browser changing the "current directory" however in principle it sounds like a good idea.
Are you suggesting that if you browse for something, and we get an absolute path, and that path happens to be inside the MUSHclient executable directory path, that it gets converted to a relative path? Or maybe throw in something like %EXECUTABLE% which gets converted back later?
Are you suggesting that if you browse for something, and we get an absolute path, and that path happens to be inside the MUSHclient executable directory path, that it gets converted to a relative path? Or maybe throw in something like %EXECUTABLE% which gets converted back later?
Nick Gammon said:
Are you suggesting that if you browse for something, and we get an absolute path, and that path happens to be inside the MUSHclient executable directory path, that it gets converted to a relative path?
Are you suggesting that if you browse for something, and we get an absolute path, and that path happens to be inside the MUSHclient executable directory path, that it gets converted to a relative path?
Yes. This one. That way if you move the MUSHclient folder to a different location the path will still be correct.