 | | (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 (...) (25 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 (...) (25 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, (...) (25 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 (...) (25 years ago, 30-Apr-99, to lugnet.cad.dev, lugnet.admin.general)
|
| |
| | Re: Unofficial Part: 30357
|
|
(...) OK, then before I finish this part, could we have a quick discussion on this among the Parts Authors? (1) (...) Big help. I get it now. Thanks :) --Karim [1] "I was not elected to watch my pieces suffer and DIE while you discuss this (...) (25 years ago, 29-Apr-99, to lugnet.cad.dev)
|
