 | | Re: Instead of ~Moved to
|
|
(...) I think there is some part of your equation that we don't realize/understand? I can view all my LDRAW models without any updating, thanks to the "moved to" concept. The models doesn't become obsolete even though the part numbers are updated. (...) (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
|
|
(...) You should take heart from the fact that this phenomenon has slowed a GREAT deal in recent times, the number of possible renumbers is way way down, and number accuracy is way up. TLG doesn't tend to switch from solid to hollow studs anymore, (...) (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 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
|
|
(...) Yes, I know my suggested approach has its obvious downsides. But the current system really makes me Yike!, too. When do we reach the point where the downsides of the current system overturn the advantages? I think we've already passed that (...) (15 years ago, 20-Jan-10, to lugnet.cad)
|
| |
| | Re: Instead of ~Moved to
|
|
(...) <snip> (...) (the "fake" number 111 sticks around, and the official design number 2222 points to it) Yikes! So you want everyone stuck with 111 for all eternity? With the current system, I'm free to remove 111.dat if I don't want it, and end (...) (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
|
|
(...) 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
|
|
(...) Advanced folks could have MovedTo directory and move all the "0 ~Moved To" files there. You can then add MovedTo to MLCad.ini to tell it about the MovedTo directory. You keep the MovedTo files (if you want), MLCad's auto update, and yet not (...) (15 years ago, 19-Jan-10, to lugnet.cad)
|
