(2022-04-25, 1:24)Travis Cobbs Wrote: so I'd like to propose that we ask Orion's opinion (since he's the third vote), and we go with whatever he recommends.
I guess that would be a solution to the deadlock
But (again) I want to make clear the only issue I'm having here, is we are (imho) in danger of standardizing something that only make things more difficult while never or hardly been used in practice.
Just because "It's always been there" is not a good enough reason for me.
Most people just trow all files in a single folder where the whole issue doesn't matter, because local==model folder.
Things get messy when subfolder models start referencing the higher ones without using "../". But I doubt people even use that.
Keeping the top level model folder in the (temporary) search list influences the context of all recursively loaded files. This means if another model uses the same submodel it (in theory, but I suspect never for real) might be (non col16) visibly different and will need instance management.
Hence my reluctance to adding this to the standard. Because it would force developers to support something (potentially extremely complicated) that is never used and easily fixable in the few cases that do need it.
One could fix it by referencing using the parent folder(s) or by simply adding a global (model) search folder to program's settings.
Both would prevent the whole messy context dependency thing and help keep the standard clean and easy to implement.