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 / 10356
10355  |  10357
Subject: 
Re: L3P-Bug using LGEO
Newsgroups: 
lugnet.cad.dev
Date: 
Wed, 16 Nov 2005 11:47:35 GMT
Viewed: 
2499 times
  
In lugnet.cad.dev, Dean Earley wrote:
Tim Gould wrote:
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.

The point is that it is not MLCad which differentiates, it is mklist.

I read Steve's email as saying that they shouldn't and that the
extension doesn't matter but IMO it does.
Rereading it, it sounds like the extension does matter but that it
shouldn't be used to identify the type of file which I agree with.

Surely the extension is entirely to identify the type of file, otherwise they
would be irrelevant?
While I understand that .dat is a widely used extension it would be foolish if
any change was to .ldr (for parts), another extension would make much more
sense. (for human AND machine differentiation between models and parts)

Tim
/me shuts up :)



Message has 1 Reply:
  Re: L3P-Bug using LGEO
 
--SNIP-- (...) IMO the best solution would be to have a magic number at the start of the parts. eg. 0 LDP or something. That way the 'partness' of each part would be quicly verified merely be reading the first five bytes of the file regardless of (...) (19 years ago, 16-Nov-05, to lugnet.cad.dev)

Message is in Reply To:
  Re: L3P-Bug using LGEO
 
(...) I read Steve's email as saying that they shouldn't and that the extension doesn't matter but IMO it does. Rereading it, it sounds like the extension does matter but that it shouldn't be used to identify the type of file which I agree with. /me (...) (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

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