(2021-03-17, 4:24)Orion Pobursky Wrote: I believe that local files (either embedded within the mpd or in the local directory) overriding library files is the de facto standard and has been since, at least, the early days of MLCad. Any default behavior the doesn't follow that standard would, in my opinion, result in unexpected output. Of course, any reasonable program can choose to allow the user to override this default with the caveat that unintended output could result.That's ok, but the thing I'm getting from this discussion is the feeling there are different rules for parts and model's.
Also the examples given are all single model ones.
O would like to define the whole spectrum of behaviour.
Including references to another mpd (sorry Travis I think this should be supported, e.g. a city made out of several houses all contained in their own mpd's)
For example what does mlcad do if you load a different model also containing a stud.dat, will all parts change or will they retain the previous version.
I'll have to do some additional research to get a better insight on the 'de-facto' way of things.