|
|
 | | Re: L3P-Bug using LGEO
|
| (...) 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, (...) (19 years ago, 14-Nov-05, to lugnet.cad.dev)
| | | | | Re: L3P-Bug using LGEO
|
| (...) The point is that it is not MLCad which differentiates, it is mklist. Tim (19 years ago, 14-Nov-05, to lugnet.cad.dev)
| | | | | 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)
| | | | | Re: L3P-Bug using LGEO
|
| (...) No, it doesn't. (...) 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 (...) (19 years ago, 14-Nov-05, to lugnet.cad.dev)
| | | | | Re: L3P-Bug using LGEO
|
| (...) Actually, there's really no easy way to do part detection, but filenames really aren't a good idea. I'm pretty sure Lars is fully aware of the part detection problem (since it also affects the seams option in L3P), and there have been (...) (19 years ago, 14-Nov-05, to lugnet.cad.dev, FTX)
|
|
