Subject:
|
Re: L3P-Bug using LGEO
|
Newsgroups:
|
lugnet.cad.dev
|
Date:
|
Mon, 14 Nov 2005 23:09:05 GMT
|
Viewed:
|
3600 times
|
| |
|
|
In lugnet.cad.dev, Dean Earley wrote:
> > I disagree because the dat and ldr extensions do not indicate the type of
> > content in the file (except that it's an LDraw file). I imagine if we ever
> > break backwards compatibility in the part library, we'll switch all the files to
> > .LDR extensions.
>
> Surely the very fact it is .ldr instead of .dat differentiates it from
> the lego parts.
No, it doesn't.
> MLCad doesn't recognise 3010.ldr as a valid part
MLCad has no such restriction - that restriction is put in place by mklist. Go
ahead - create parts/3010.LDR, edit parts.lst, add 3010.LDR and a description,
it will magically appear in MLCad and be usable just as any other part.
ROSCO
|
|
Message has 1 Reply:
 | | Re: L3P-Bug using LGEO
|
| (...) But that DOES differentiate between .dat and .ldr by the very fact it has the extension in parts.lst. If it didn't, 3010.dat and 3010.ldr would be interchangeable everywhere. This means that 3010.dat is NOT the same as 3010.ldr but L3P appears (...) (20 years ago, 14-Nov-05, to lugnet.cad.dev)
|
Message is in Reply To:
| | Re: L3P-Bug using LGEO
|
| (...) Surely the very fact it is .ldr instead of .dat differentiates it from the lego parts. MLCad doesn't recognise 3010.ldr as a valid part, and it allows both blah.dat and blah.ldr in the same mpd file. (20 years ago, 14-Nov-05, to lugnet.cad.dev)
|
19 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
