|
 | | 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
|
| 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
|
| 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
|
| 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
|
| (...) 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)
| |