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 / 1539
1538  |  1540
Special: 
[DAT] (requires LDraw-compatible viewer)
Subject: 
Re: "~moved to" files and parts.lst
Newsgroups: 
lugnet.cad.dev
Date: 
Wed, 28 Apr 1999 06:17:08 GMT
Viewed: 
701 times
  
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.

The cut'n'paste approach assumes that shortcut files will always reference
the new part with a standard line:
  1 16 0 0 0  1 0 0  0 1 0  0 0 1 5678.dat
Is this always going to be true?  Probably, but it's a bad assumption to
make.

AFAIK, it should be true.  That is the standard call to use in a ~Moved to
file.   I don't see any reason to alter it.

We've discussed re-aligning parts when/if they are moved to a new number,
and what about hard-coded colors?

There shouldn't be any effect.  I think.
The hard-coded part _should_ just be a shortcut file that calls the basic
piece.  If the number of the basic piece changes, then the hard-coded shortcut
_should_ get updated as well.  But even if it is missed, it should still point
to the ~Moved to file, which would still work.

-- Terry K --



Message has 1 Reply:
  Re: "~moved to" files and parts.lst  [DAT]
 
(...) Part #30079 is mis-positioned. It is not aligned for easy placement. I don't remember the exact numbers, maybe you have to move the piece up by -3LDU to 'click' it into a model, I don't remember. There was discussion about correcting the part, (...) (25 years ago, 28-Apr-99, to lugnet.cad.dev)

Message is in Reply To:
  Re: "~moved to" files and parts.lst  [DAT]
 
(...) 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 (...) (25 years ago, 27-Apr-99, to lugnet.cad.dev)

11 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