| |
On 21-Aug-2002, "Erik Olson" <erik@olson.pair.com> wrote:
> 3. Keep the exact part filename specified, even if slightly different on
> host computer (example: when shield.dat maps to SHIELD.dat, or even
> shield.ldr)
> 4. Preserve indentation, maybe even try to mimic it when a new part is
> inserted to a step (as in pyramid.dat which has indentation)
These 2 are the 2 biggest problems I have with MLCAD.
For some reason MLCad changes the filename in the NAME comment block to an
.ldr extension even if the source file is .dat. As more of a part author
than a model builder, this is very annoying.
MLCad also destroys any blank lines in a file, gets rid of any 0 lines
without a comment, and destroys indentation. I realised this after
carefully formatting my DAT file only to have my formatting completely wiped
out by MLCad.
Keep in mind that these are only very minor annoyances and not major flaws
in the program
-Orion
|
|
Message has 1 Reply:
 | | Re: DAT files: Do No Harm
|
| (...) This sounds counter-productive to me. Judging from the official LDraw files, it appears that many of the original files follow these guidelines with respect to indentation: o Comments are not indented o All other lines are indented by one (...) (22 years ago, 22-Aug-02, to lugnet.cad.dev, lugnet.cad.mlcad)
|
Message is in Reply To:
| | DAT files: Do No Harm
|
| What consideration should an editor program make for unfamiliar content or eccentric style when it loads and saves an LDRAW file with changes? I am implementing the following general ideas in BrickDraw3D, based on various situations in test files. (...) (22 years ago, 21-Aug-02, to lugnet.cad.dev)
|
14 Messages in This Thread:
  
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
