(2021-03-17, 7:08)Roland Melkert Wrote: 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.
I don't understand what you mean by different rules for parts and models. The rules are the same for all files, but the directory containing the top-level file is treated as being special (being the second entry in the path lookup right after mpd-contained files).
We can come up with rules for mpds inside of other mpds.