Subject:
|
Re: L3P-Bug using LGEO
|
Newsgroups:
|
lugnet.cad.dev
|
Date:
|
Mon, 14 Nov 2005 23:28:29 GMT
|
Viewed:
|
2337 times
|
| |
|
|
In lugnet.cad.dev, Dean Earley wrote:
> > 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.
>
> 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 to
> think they are regardless of path/location. 3010.ldr is not a (current)
> lego part and should not be treated as such.
I don't think L3P pays any attention to parts.lst. To be honest, I don't think
that it should. It's not an editor that's expected to give you a list of parts
available for use. (And to be honest, I think that parts.lst is a generally bad
idea, because the user is expected to update it, which isn't user-friendly.)
--Travis
|
|
Message is in Reply To:
 | | 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 (...) (19 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
|
|
|
|
