This could also be implemented on a project by project by project basis with each project having the absolute/relative option stored in the webdown.dat file. It would only need to be written to the webdown.dat file if you wanted to have relative links, meaning no change to anyone ignoring the option.
Alternatively (I think this is the best option) OE could have two global variables
- one to define relative/absolute mpx files
- one to define downloaded file locations (this one already exists)
Then each project could also have two variables which could override these:
- One could be set to “inherit global”/”relative”/”absolute” and only stored in the webdown.dat file if it changed from global.
- The second could define the download location for that project as “inherit global”/”user defined location” and again only be stored in the webdown.dat file if it changed from the global.
This way, if the global setting was set to “absolute” by default, any user that ignored these features would see no change in operation or their webdown.dat file. Any user that wanted to move their download location could simply define mpx files as “relative” as the global option and change the download location option and be up and running again straight after the move. Also, specific projects could be given their own download location if required.