 | | Re: DAT format question
|
|
My original plans called for my CAD package to distinguish among the various kinds of DAT file. This would allow the program to know when it was appropriate to enable certain editing features. For example, it shouldn't allow the user to add (...) (25 years ago, 21-Sep-99, to lugnet.cad.dev)
|
| |
| | Re: DAT format question
|
|
(...) I don't see that as being that big a deal, really. And if you could have some kind of button on a toolbar for each of them, all the better. (25 years ago, 21-Sep-99, to lugnet.cad.dev)
|
| |
| | Re: DAT format question
|
|
Gary Williams wrote in message ... (...) with. Doh', this wouldn't be a complete solution, either. If the user opens a model, I'd still have to determine which external references in it are parts and which are embedded models/subassemblies. And if (...) (25 years ago, 21-Sep-99, to lugnet.cad.dev)
|
| |
| | Re: DAT format question
|
|
Would it be too restrictive of my CAD program to require that all parts (and nothing but parts) are stored in the parts and parts/s directories, and all primitives (and nothing but primitives) are stored in the p directory? Models could exist (...) (25 years ago, 21-Sep-99, to lugnet.cad.dev)
|
| |
| | Re: DAT format question
|
|
(...) Why not? I've done this when a part didn't exist (I used a box.dat for the center of the 1x2x2 shock absorber) (...) Part developers often use different colors to make sure shapes are matching up correctly. Also, atterned parts and some other (...) (25 years ago, 22-Sep-99, to lugnet.cad.dev)
|
| |
| | Re: DAT format question
|
|
(...) Probably too restrictive. Most (I think) part developers design their parts in the models directory to keep them separate from the official parts. Mock-ups and crude outlines of parts should also be kept out of the parts directory. I like the (...) (25 years ago, 22-Sep-99, to lugnet.cad.dev)
|
| |
| | Re: DAT format question
|
|
Bram Lambrecht wrote in message <19990921.200045.509...no.com>... (...) My experience has been that as flexibility increases, complexity increases. I'm usually quite anal about coding objects to always behave in a very structured, predictable (...) (25 years ago, 22-Sep-99, to lugnet.cad.dev)
|
| |
| | Re: DAT format question
|
|
Gary Williams: (...) This makes sense for the editor, but the renderer should consider any LDraw file equal wherever it resides. It it also worth remembering that some parts files actually uses specific colours (not only 16 and 24). Play well, Jacob (...) (25 years ago, 22-Sep-99, to lugnet.cad.dev)
|
| |
| | Re: DAT format question
|
|
Gary Williams: (...) [...] (...) Then give the user a _choice_ of interface. (...) I would limit command types 2-5 to the "extended interface". (...) The selected object would of cause (imo) always be the level referred directly to by the root level (...) (25 years ago, 22-Sep-99, to lugnet.cad.dev)
|
| |
| | Re: DAT format question
|
|
(...) For new files, LDAO allows the user to specify the type of the file, separate from its location. The type information is written to the file as part of the header lines. When a file is loaded, LDAO looks for the typing information. If the file (...) (25 years ago, 22-Sep-99, to lugnet.cad.dev)
|
| |
| | Re: DAT format question
|
|
(...) Complexity also increases as over-specification increases. (...) Yes, polygons and lines should be allowed. Maybe that should be on the advanced interface, but it should be allowed. (...) Yes. (...) Exactly. And if you right-click an object, (...) (25 years ago, 22-Sep-99, to lugnet.cad.dev)
|
| |
| | Re: DAT format question
|
|
Steve Bliss wrote in message <37e9033a.13891366@l...et.com>... (...) Yup. The simplified one I made last night is here: (URL) over-complicated one isn't on the server anymore. -Gary (25 years ago, 22-Sep-99, to lugnet.cad.dev)
|
