 | | Re: MPD file loading search order
|
|
(...) Well, if you read all postings on MPD through the last seven years you should be able to piece the correct answer together :-) I believe the L3 parser (used in L3P, L3Lab and "ldglite -l3") reflects that information. > However, I can tell (...) (18 years ago, 25-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: MPD file loading search order
|
|
(...) Sorry, you're right every part in the mpd should see any of the other parts. May be Ldraw.org should post a set of 'testcase' files to be used as a reference for programmers. For each file there should be a description of the expected results (...) (18 years ago, 25-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: MPD file loading search order
|
|
(...) Is that what I said? I didn't mean to... If an MPD contains main.dat, a.dat, and b.dat, then a.dat should be able to 'see' b.dat. I make heavy use of the MPD format while working on part files. Inside a single MPD, I typically have long chains (...) (18 years ago, 25-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: MPD file loading search order
|
|
(...) You can do it in one pass (if you don't count the loading of the file to a stringlist). Wile walking through the file you build you're objectlist with subparts. Afterwards you go recursively through the list of subparts. This way all mpd (...) (18 years ago, 25-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: MPD file loading search order
|
|
(...) Snip, very thourho explanation, thanks! (...) I was thinking of doing the local scope approach mentioned by Steve. But maybe I keep it optional realizing I always end up disappointing some people with ether approach. I was planning to create (...) (18 years ago, 25-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: MPD file loading search order
|
|
(...) I mentioned in my other (long) post that I don't think that MPD files should be required to have a .mpd extension. However, I'd like to add more here in answer to your specific question. I could be wrong, but I'm almost positive that it is (...) (18 years ago, 25-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: MPD file loading search order
|
|
As you have pointed out, the spec is indeed ambiguous. Consequently, there's probably no correct answer as to how things should work. However, I can tell you what I do in LDView, so that you have an idea of how at least one MPD-compatible program (...) (18 years ago, 25-Jul-06, to lugnet.cad.dev, FTX)
|
| |
| | Re: MPD file loading search order
|
|
Thanks Tim and Steve, I think I will go with Steve's advise to let only the main part in the mpd see the other parts in the mpd. This will give a much cleaner recursive approach, in which I can easily support sub mpd's. Further more I think I will (...) (18 years ago, 25-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: MPD file loading search order
|
|
(...) Tim pointed you at the actual MPD spec. You may notice that is is vague on a lot of points -- it basically leaves it up to the program authors. My comments below are what makes sense to me, thinking as someone who might create complex MPDs. (...) (18 years ago, 25-Jul-06, to lugnet.cad.dev)
|
| |
| | Re: MPD file loading search order
|
|
(...) My apologies. I just looked there more closely and it doesn't seem to answer anything. To answer what I'm fairly sure of (but far from certain): I think that the correct lookup order is internal, ., [MODELS], [PARTS] Yes MPD files must have (...) (18 years ago, 25-Jul-06, to lugnet.cad.dev)
|
