 | | Re: ldglite (ldlite for OpenGL and Linux) new stuff
|
|
Paul: [ Tells us that we are behaving a little bit silly. ] You are probably right, but... I think that the main problem is that practically none of us are experienced CAD developers or users. Some of Paul's points: - Different coordinate systems I (...) (25 years ago, 4-Feb-00, to lugnet.cad.dev)
|
| |
| | Re: L-Draw - Future is the Net?
|
|
People who find it slow could download a distribution to a local directory. LDRAW tools should have a search path that the user can edit, so local directories could be looked at first. Good point about testing. Mounting a drive (using whatever (...) (25 years ago, 4-Feb-00, to lugnet.cad.dev)
|
| |
| | Re: Reading Part-Lists (was: Suggestion for MLCad Plug-Ins)
|
|
Steve Bliss skrev i meddelandet ... (...) Well, I supposed I asked for it :-)) -- Anders Isaksson, Sweden BlockCAD: (2 URLs) (25 years ago, 4-Feb-00, to lugnet.cad.mlcad, lugnet.cad.dev)
|
| |
| | Re: L-CAD Parts Messages (was: Suggestion for ML-CAD Plug-Ins)
|
|
Steve Bliss skrev i meddelandet <+PCaOHXM4TXRXiZv7pF...ax.com>... (...) assuming (...) only (...) Not really, assuming a very long message *really* works, but I suppose there is no reason why it shouldn't. Multi-message is always more complicated (...) (25 years ago, 4-Feb-00, to lugnet.cad.dev, lugnet.cad.mlcad)
|
| |
| | Re: I need help with MLCad
|
|
(...) Well there you go then. (...) I have a perfect record. I've never been turned down when I asked for a part to be created. Before you attribute that to my godhood, I should point out that I've never asked. :-) (25 years ago, 4-Feb-00, to lugnet.cad.mlcad)
|
| |
| | Re: I need help with MLCad
|
|
(...) Nope, not to lcdp. Only postings of part files should go there (but follow-ups to part-postings are allowed). To request parts, post to lugnet.cad or lugnet.cad.dev. Historically, requesting parts has been a low-percentage game. But sometimes (...) (25 years ago, 4-Feb-00, to lugnet.cad.mlcad)
|
| |
| | Re: LDraw CD-ROM Project
|
|
(...) Which is why I suggested it. Look, my point is just this: before 1800 is shelled out, make sure that you have some reasonable expectation of recovering all or most of it. I'll gladly put up a hundred bucks to make this happen, with no (...) (25 years ago, 4-Feb-00, to lugnet.cad.dev)
|
| |
| | Re: Colors for pneumatic cylinder (was Re: Looking for broken pneumatics)
|
|
(...) Since they are available with various colors for the cap, it's even more important to do a separate file for each component. But the leaf-files are *parts*, not *sub-parts*. Probably with a tilde on the front of the part-title. Steve (25 years ago, 4-Feb-00, to lugnet.cad.dev)
|
| |
| | Reading Part-Lists (was: Suggestion for MLCad Plug-Ins)
|
|
(...) Hmm. Keep a list of field names in a text file. This list maps the field names in various inventory lists to the actual field names. Ex: Part,Part PartID,Part PartNo,Part Name,Name Desc,Name Color,Color Colour,Color Quantity,Quantity (...) (25 years ago, 4-Feb-00, to lugnet.cad.mlcad, lugnet.cad.dev)
|
| |
| | L-CAD Parts Messages (was: Suggestion for ML-CAD Plug-Ins)
|
|
(...) The second approach went beyond the event horizon. (...) One long message with line separators. As long as WM_COPYDATA permits, assuming WM_COPYDATA specifies a limit. <reads doc> Yeah, there's a limit. We can only have 2^32 bytes in the (...) (25 years ago, 4-Feb-00, to lugnet.cad.mlcad, lugnet.cad.dev)
|
