(2022-03-16, 0:38)Travis Cobbs Wrote: Having said that, the top-level model folder still makes sense if you think of that folder as the current working directory for the whole model. Adding the current file's directory to the search path is reasonable, but I don't think it should replace the top-level model's directory. What about this:
What would be the advantage of that?
I can only see it causing potential problems, expanding on my above example.
If the b.ldr model want to use something from the higher folder it should reference it using "..\d.ldr" otherwise it will (again) fail to load when opening just b.ldr.
And also it will complicate things for programs working with multiple open models at once.
Because you will need to keep track of how a model was opened.
It will cause two different 'b.ldr' instances when a user first opens b.ldr standalone and later also opens 'a.ldr' in the same program.
The first b.ldr will indicate missing references and the second one will display fully keeping track of this will need lots of house keeping without gaining, imho, any advantage over not including the working folder at all.
In short every model should live in it's own little universe fully isolated from anything else loaded.
This way you can work with multiple open models without the scoping problems a 'working folder' would cause.
Also when will it even be needed?
You say you think there are no real multi folder models out there, which would mean the <current file folder> and <working folder> would be the same for almost all models (at least in your experience).
So what would be the point of adding it to the search order causing all these headache's for developers