 | | Re: "~moved to" files and parts.lst —Manfred Moolhuysen
|
| | | -----Original message----- From: Terry K <legoverse@geocities.com> To: lugnet.cad.dev@lugnet.com <lugnet.cad.dev@lugnet.com> Date: donderdag 22 april 1999 2:43 Subject: "~moved to" files and parts.lst (...) I agree. Greetings, M. Moolhuysen. (25 years ago, 23-Apr-99, to lugnet.cad.dev)
|
| | | |
| | | | | Re: "~moved to" files and parts.lst —Tore Eriksson
|
| | | | I agree, but shouldn't we have a separate moved-to.lst file? /Tore (...) (25 years ago, 23-Apr-99, to lugnet.cad.dev)
|
| | | | |
| | | | | | Re: "~moved to" files and parts.lst —Terry Keller
|
| | | | (...) We could. If Steve and Lars would be willing to code their respective list programs to do so. I am not sure of the need or utility of having it, though. Any thoughts on what it would be useful for? AFAIK, LDraw, LDLite, and LDAO's Part Updater (...) (25 years ago, 24-Apr-99, to lugnet.cad.dev)
|
| | | | |
| | | | | | Re: "~moved to" files and parts.lst —Steve Bliss
|
| | | | | (...) Oo. That one gets a big "I don't remember" from me. I am in the middle of re-writing the way LDAO checks & maintains parts.lst & the VEC, so I could easily add some extra code for a moved-to list. Steve (25 years ago, 24-Apr-99, to lugnet.cad.dev)
|
| | | | | |
| | | | | | Re: "~moved to" files and parts.lst —Steve Bliss
|
| | | | (...) I double-checked this, and what Terry says is true for LDAO. Which is good. The bad news is that LDAO simply replaces the old part number with the new part number. It should be doing an inline operation. Steve (25 years ago, 26-Apr-99, to lugnet.cad.dev)
|
| | | | |
| | | | | | Re: "~moved to" files and parts.lst —Terry Keller
|
| | | | (...) (whew!) Glad my assumption was correct. :-) (...) Huh? What do you mean by inline operation? -- Terry K -- (25 years ago, 27-Apr-99, to lugnet.cad.dev)
|
| | | | |
| | | | | | Re: "~moved to" files and parts.lst —Steve Bliss
|
| | | | (...) 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)
|
| | | | |
| | | | | | Re: "~moved to" files and parts.lst —Terry Keller
|
| | | | (...) 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, (...) (25 years ago, 28-Apr-99, to lugnet.cad.dev)
|
| | | | |
| | | | | | Re: "~moved to" files and parts.lst —Steve Bliss
|
| | | | (...) 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)
|
| | | | |
| | | | | | Re: "~moved to" files and parts.lst —Terry Keller
|
| | | | (...) Ah..... Now I see your point. That would be a valuable feature, if we moved a part slightly using the ~moved to file. And it would have no affect on a part that has not been re-positioned in the ~moved to file. While an interestion conjecture, (...) (25 years ago, 30-Apr-99, to lugnet.cad.dev)
|
| | | | |
| | | | | | (Was: "~moved to" files) —Tore Eriksson
|
| | | | I have not followed this thread so carefully (either) but I think if we ever move wheel- or tyre file, we should use one x~z direction, prefarably the current most commonly used. I find it quite frustration that wheels don't point the same way. Or (...) (25 years ago, 30-Apr-99, to lugnet.cad.dev)
|
| | | | |
