To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.cad.devOpen lugnet.cad.dev in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 CAD / Development / 10341
10340  |  10342
Subject: 
Re: L3P-Bug using LGEO
Newsgroups: 
lugnet.cad.dev
Date: 
Mon, 14 Nov 2005 22:06:35 GMT
Viewed: 
2450 times
  
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.
MLCad doesn't recognise 3010.ldr as a valid part, and it allows both
blah.dat and blah.ldr in the same mpd file.

--
Dean Earley, Dee (dean@earlsoft.co.uk)

irc:    irc://irc.blitzed.org/
web:    http://personal.earlsoft.co.uk
phone:  +44 (0)780 8369596



Message has 1 Reply:
  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)

Message is in Reply To:
  Re: L3P-Bug using LGEO
 
I agree and disagree with this. I agree that it would be good (for now) if L3P only substituted LGEO parts for files with a .dat extension. Or, even better, if (a) the file being substituted has the UNOFFICIAL/LDRAWORG meta-statement and states it (...) (19 years ago, 14-Nov-05, to lugnet.cad.dev, FTX)

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
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR