To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.cadOpen lugnet.cad in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 CAD / 16876
  Re: Instead of ~Moved to
 
Tore, I'm not really seeing the problem in the parts\s directory - there are 18 "moved to" files there. My parts directory has 456 "moved to" files, but there's not really any way around having those -- they serve two purposes: a) provide backwards (...) (15 years ago, 19-Jan-10, to lugnet.cad)
 
  Re: Instead of ~Moved to
 
(...) For some reason, those 18 "moved to" files in parts\s make a lot of noise for me. I know they shouldn't but they do and I haven't figured out the reason yet. There is another problem. It is kind of subtile, so I don't know if I'm able to (...) (15 years ago, 20-Jan-10, to lugnet.cad)
 
  Re: Instead of ~Moved to
 
(...) <SNIP> (...) The problem is that it doesn't. As I pointed out in my latest post, (URL) , almost every single existing LDraw model file ever made needs to be updated with every parts update realeasd. That has absolutely nothing to do with true (...) (15 years ago, 20-Jan-10, to lugnet.cad)
 
  Re: Instead of ~Moved to
 
(...) I don't understand what you're saying here, Tore. The ~Moved To files prevent the need to update already existing files by providing a back reference to the old part number. This prevents a part from disappearing from a model simply because (...) (15 years ago, 20-Jan-10, to lugnet.cad)
 
  Re: Instead of ~Moved to
 
(...) Hmmm, subparts are used by many parts so I can see how they might be referenced a gazillion times by an extremely large model file like Datsville. (...) What tool makes the movedto.log file that's giving you such trouble? Can it be adjusted to (...) (15 years ago, 20-Jan-10, to lugnet.cad)
 
  Re: Instead of ~Moved to
 
(...) I was going to start my response with "I don't understand", but Orion beat me to it. It is absolutely not necessary to update existing models with the replacement file referred to by the "~Moved to" file, but maybe I am missing something about (...) (15 years ago, 20-Jan-10, to lugnet.cad)
 
  Re: Instead of ~Moved to
 
In lugnet.cad, Chris Dee wrote: snip (...) The zip archive's chief virtue is not its familiarity, but its cross-platform portability. It's very important to maintain that. (...) I fixed that Bricksmith bug about a year and a half ago, so you don't (...) (15 years ago, 22-Jan-10, to lugnet.cad, FTX)
 
  Re: Instead of ~Moved to
 
In lugnet.cad, Allen Smith wrote: <SNIP> (...) Depending on their viewpoint and experience with LDraw, different users might argue that either inclusion OR exlclusion can be confusing. By including both in the library and providing a way to identify (...) (15 years ago, 25-Jan-10, to lugnet.cad, FTX)

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