 | | Instead of ~Moved to [DAT]
|
|
To me, all these "~Moved to" files are just trouble and extra work and lots of extra files in the Parts, Parts\S, and P folders. And for each parts update, the extra work and problems seem to increase exponentially. I know, one can say some of the (...) (15 years ago, 19-Jan-10, to lugnet.cad)
|
| |
| | Re: Instead of ~Moved to
|
|
(...) SNIP (...) I agree with you! I have to think about the way we have to go with this new approach for the many possible reasons of changing things, but at first look it could be a nice way to minimize admin edit work. Maybe we will have both (...) (15 years ago, 19-Jan-10, to lugnet.cad)
|
| |
| | Re: Instead of ~Moved to
|
|
I also agree that the current system is...extravagant. 'litter files' also seems like an appropriate term for the thousands of unnecessary files that clutter my LDraw library. Personnally, I'd like my library to only have actual parts; no ~Moved to (...) (15 years ago, 19-Jan-10, to lugnet.cad)
|
| |
| | Re: Instead of ~Moved to
|
|
(...) I'm not much of an expert in this area, but that never stops me from shooting my mouth off! On unix (e.g. Mac), it would be easy enough to use grep/find to find the files that contain "0 ~Moved to" and simply remove them. Cygwin on Windows (...) (15 years ago, 19-Jan-10, to lugnet.cad)
|
| |
| | 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
|
|
(...) Yes, another method will break MLCad's update mechanism. I also like that. But maybe also another solution will work that way, but it has to be implemented. On the other side if we use the proposed way you also will have the latest geometrie (...) (15 years ago, 19-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)
|
| |
| | 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
|
|
(...) <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
|
|
(...) 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
|
|
(...) 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 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
|
|
(...) 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
|
|
(...) 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)
|
