 | | | | | | |
| |
|
In lugnet.cad, Kevin L. Clague wrote:
> In lugnet.cad, Steve Bliss wrote:
> > BTW, there are at least 2 reason not to use MLCAD to create parts which you want
> > to contribute to LDraw.org:
> >
> > 1. (General reason) it's more work than doing it in an enhanced text editor.
> > 2. (Specifically) MLCAD does things to the file that are not allowed in official
> > part files, so you have to clean up the code afterwards (and then you can no
> > longer edit it in MLCAD).
>
> Ummmm.... given that.... could you be so kind as to tell me what those are?
> This way I can choose to/or not use MLCad and then clean things up afterwards.
I did a quick test with MLCAD 3.11 and noticed the following:
(Opened a partfile in MLCAD and save it under a different filename
and then compared the two files)
MLCad adds two rotation commands to the header
0 ROTATION CENTER 0 0 0 1 "Custom"
0 ROTATION CONFIG 0 0
MLCad replaces every
0 BFC INVERTNEXT
with
0 BFC CERTIFY INVERTNEXT
No harmfull things are:
MLCad removes unnesseccary spaces and empty lines
MLCad replaces numbers as 3.10 with 3.1
MLCad replaces numbers as .123 with 0.123
Niels
| | | | | | | | | | | | | | |
In lugnet.cad, Niels Karsdorp wrote:
> I did a quick test with MLCAD 3.11 and noticed the following:
> (Opened a partfile in MLCAD and save it under a different filename
> and then compared the two files)
Thanks for doing this, Niels.
> No harmfull things are:
> MLCad removes unnesseccary spaces and empty lines
When creating part files, I frequently add 'unnecessary' spaces and empty lines
to improve (IMO) readability.
> MLCad replaces numbers as 3.10 with 3.1
> MLCad replaces numbers as .123 with 0.123
Change-tracking is much simpler if lines of code aren't changed unless they
actual need to be changed. For people making new parts, MLCad's forced-format
isn't a big deal. When people update/correct official files, I consider MLCad's
forced-format changes to be hostile to the update process.
Steve
| | | | | | |
