 | | Re: [Part] 3841.dat Minifig Tool Pickaxe
|
|
(...) improving (...) the (...) lines (...) me (...) of (...) One (...) Thank you, John Van and Terry for the valuable comments. It seems to me that it worths to incorporate your suggestions into the part. I going to resubmit it with the suggested (...) (26 years ago, 30-Apr-99, to lugnet.cad.dev)
|
| |
| | (Was: "~moved to" files)
|
|
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 (...) (26 years ago, 30-Apr-99, to lugnet.cad.dev)
|
| |
| | Re: "~moved to" files and parts.lst
|
|
(...) Sure do. I just did not make the mental connection between that idea and inlining parts during an "update parts" process. As I recall, updating of parts was the primary reason not to do this. Steve's idea for inlining the part would solve that (...) (26 years ago, 30-Apr-99, to lugnet.cad.dev)
|
| |
| | Re: "~moved to" files and parts.lst
|
|
(...) 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, (...) (26 years ago, 30-Apr-99, to lugnet.cad.dev)
|
| |
| | Re: lugnet.cad hierarhcy
|
|
(...) Yes. I'm thinking that the safest & quickest (at runtime) approach will be to embed a special header into the NNTP article stream just as it's being injected by the newsserver (similar to the way the default Followup-To field is automatically (...) (26 years ago, 30-Apr-99, to lugnet.cad.dev, lugnet.admin.general)
|
