 | | Re: Straightening Up the MPD Format
|
|
(...) I just tried your kd-bi.mpd that you have exported from LeoCad. Is that pure export? I am asking because those "embedded" files lacks an important line "0 Name: xyz". And for that MPDCenter does not recognize that files. cu mikeheide (15 years ago, 2-Apr-10, to lugnet.cad)
|
| |
| | Re: Straightening Up the MPD Format [DAT]
|
|
(...) No, current version doesn't support mpd (next one will). But compositing files were coming from LeoCAD. (...) Here below a sample MPD created with upcoming LeoCAD version. Please make comments here, I'll tell Leonardo. Philo 0 FILE Main_model (...) (15 years ago, 2-Apr-10, to lugnet.cad)
|
| |
| | Re: Straightening Up the MPD Format
|
|
(...) O NAME is not required for ordinary ldraw files, only official library parts. The only Meta command needed to assemble an mpd file is 0 FILE, so the mpd file from LeoCAD is fine as is. Don (15 years ago, 2-Apr-10, to lugnet.cad)
|
| |
| | Re: Straightening Up the MPD Format
|
|
(...) Then the problem is at MPDCenter. 0 Name is a very good and recommended habit, but not currently required. But I have thought of using 0 Name to solve this problem. When exploding an MPD, the user may be prompted to either use the unique 0 (...) (15 years ago, 2-Apr-10, to lugnet.cad)
|
| |
| | Re: Straightening Up the MPD Format
|
|
(...) As 0 NAME is not required the only possible way of identifying a parts name is the content in the 0 FILE entry. So I have now two ways to go. 1) Only take the 0 FILE entry 2) If there is no 0 NAME entry - create one on the fly at MPD loading. (...) (15 years ago, 2-Apr-10, to lugnet.cad)
|
| |
| | Re: Straightening Up the MPD Format
|
|
(...) If we ever get there to create an MPD standard, I would suggest way #2: Making 0 NAME compulsary in MPD-ed files. A good safety precaution would be to prompt user if 0 NAME data is present but doesn't match actual file name: * Rename file and (...) (15 years ago, 4-Apr-10, to lugnet.cad)
|
