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 / 7934
7933  |  7935
Subject: 
Re: Formalizing a method for handling synthesizable parts
Newsgroups: 
lugnet.cad.dev
Date: 
Sun, 6 Oct 2002 16:19:11 GMT
Viewed: 
708 times
  
In lugnet.cad.dev, Kevin Clague writes:
Orion,
I had not thought about this.  This is consistant with Steve Bliss'
concern about putting out the synthesized parts in a seperate file so that
they can be cosidered one part by other LDRAW compatible programs.

I can see two issues here.  The first is simply "what do I name this
external file?"  I just have to figure out the specification for this issue.

The other issue is deeper.  For electric cables, lsynth actually knows
nothing about the ends of the cables (rotation sensor, light sensor, 2x2
connectors.)

You could always train it to know (and do it in a data file driven way so
it's easy to add new types)


It only knows where the synthesized parts are.  It seems counter intuitive
that the cable ends would be in one file and the cable middle is in a
different file.  Maybe I'll just ignore this incongruity for now.

2 levels of subfiles perhaps??? one subfile for the part which contains the
synthesized part reference (another subfile) as well as references to the ends?



Message is in Reply To:
  Re: Formalizing a method for handling synthesizable parts
 
Orion, I had not thought about this. This is consistant with Steve Bliss' concern about putting out the synthesized parts in a seperate file so that they can be cosidered one part by other LDRAW compatible programs. I can see two issues here. The (...) (22 years ago, 6-Oct-02, to lugnet.cad.dev)

37 Messages in This Thread:









Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

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