(2021-03-16, 19:43)Roland Melkert Wrote: You could do that by adding your custom/development library paths in front of the official ones.
The main thing I'm disliking about the global scope thing is the fact an embeded file which happens to have the same name as some official part would break all dependencies.
The 'context' method will only affect its local scope so there will never be problems with duplicate names, it's comparable with local variables in a programming language.
At this point in time, I think it's safe to say that if a user embeds a *.dat file in their MPD, they intend it to replace the *.dat file of that same name in the LDraw parts library. Nobody should be using *.dat for personal files anymore. So I still feel that this global replacement is correct.
Note that putting files alongside the main model to do the same thing is a leftover from the days before MPDs. However, I still think that it is consistent to continue with this behavior.