Subject:
|
Re: "~moved to" files and parts.lst
|
Newsgroups:
|
lugnet.cad.dev
|
Date:
|
Fri, 30 Apr 1999 07:07:25 GMT
|
Viewed:
|
1443 times
|
| |
|
|
On Wed, 28 Apr 1999 07:35:26 GMT, "Adviesbureau Noord/Zuidlijn"
<nzlijn@euronet.nl> wrote:
> -----Original message-----
> From: Terry K <legoverse@geocities.com>
> To: lugnet.cad.dev@lugnet.com <lugnet.cad.dev@lugnet.com>
> Date: woensdag 28 april 1999 8:18
> Subject: Re: "~moved to" files and parts.lst
>
>
> > On Tue, 27 Apr 1999 13:10:01 GMT, blisses@worldnet.att.net (Steve Bliss)
> > wrote:
>
> > > On Tue, 27 Apr 1999 09:44:37 GMT, legoverse@geocities.com (Terry K) wrote:
>
> > > > > The bad news is that LDAO simply replaces the old part number with the
> > > > > new part number. It should be doing an inline operation.
>
> > > > Huh? What do you mean by inline operation?
>
> > > If part 1234.dat was ~Moved to 5678.dat, when LDAO updates
> > > 1 16 0 0 0 1 0 0 0 1 0 0 0 1 1234.dat
> > > it shouldn't just cut out the 1234 and paste in 5678. It should inline
> > > this line (skipping any comment lines, of course). This would have the
> > > effect of grabbing the actual short-cut reference out of 1234.dat.
>
> > Something is just not clicking in my noggin. It seems to me that all you
> > would want to replace would be the filename.
> > Are you saying that the mover should grab the _entire_ line:
> > 1 16 0 0 0 1 0 0 0 1 0 0 0 1 5678.dat
> > from the ~Moved to file, and paste that entire line in place of the
> > reference to 1234.dat in the model?
>
> > But if that is what you propose, it would screw things up. If my model has
> > a line like:
> > 1 0 234 16 -46 1 0 0 0 1 0 0 0 1 1234.dat
> > I would not want that line to be changed to:
> > 1 16 0 0 0 1 0 0 0 1 0 0 0 1 5678.dat
> >
> > Now tell me what I am misunderstanding.
>
> Terry, do you remember this: (note: this is just an example, and has no
> further status)
>
> Suppose 70358 is a not_colour_specific number for the Electric Train Motor
> part, and we decide to change the insertion point (that´s where 0,0,0 is) to
> a another location.
> Then I make a 70358.DAT file with the insertion point 8 LDU lower than it
> was in the original 590.DAT file. 590.DAT would be changed into:
>
> 0 ~Moved to 70358
> 0 WRITE Part 513 moved to 70358
> 1 16 0 8 0 1 0 0 0 1 0 0 0 1 70358.dat
>
> Suppose that in an old model file you have this line:
>
> 1 16 0 -24 0 1 0 0 0 1 0 0 0 1 590.dat
>
> If you inline that "part" line the result would be:
>
> 1 16 0 -16 0 1 0 0 0 1 0 0 0 1 70358.dat
>
> And this is exactly what we want to happen.
>
> Greetings, Manfred Moolhuysen.
Sure do. I just did not make the mental connection between that idea and
inlining parts during an "update parts" process.
As I recall, updating of parts was the primary reason not to do this. Steve's
idea for inlining the part would solve that problem.
-- Terry K --
|
|
Message is in Reply To:
 | | Re: "~moved to" files and parts.lst [DAT]
|
| -----Original message----- From: Terry K <legoverse@geocities.com> To: lugnet.cad.dev@lugnet.com <lugnet.cad.dev@lugnet.com> Date: woensdag 28 april 1999 8:18 Subject: Re: "~moved to" files and parts.lst (...) Terry, do you remember this: (note: (...) (27 years ago, 28-Apr-99, to lugnet.cad.dev)
|
2 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
