| |
In lugnet.cad.mlcad, Michael Lachmann writes:
> [...]
> Version 1.6 and custom colors:
> It is true that custom colors are not useable for LView or LEdit since the
> custom colors are none-compatible extensions to the file format.
>
> When using "custom" or "redefined" colors you have to use MLCad to view the
> model.
Could you avoid writing out the file as a ".DAT" file extension if you are
making extensions to the long established LDraw DAT file format?
This would clear up confusion right away and avoid further incompatibility
issues if other LDraw-clone programs take such liberties as well.
Or, alternatively, is there something in the header of the DAT files that
MLCad writes which clearly designates it as having been written from MLCad
and thus is a non-standard format?
--Todd
|
|
Message has 1 Reply:
 | | Re: General Comments to MLCad
|
| (...) It would be better (IMO) to format non-LDraw information as LDraw-style meta-commands, and keep everything in the DAT format. That gives the file the widest transportability between programs. Steve (25 years ago, 20-Dec-99, to lugnet.cad.mlcad, lugnet.cad.dev)
|
Message is in Reply To:
| | General Comments to MLCad
|
| Since I got various responses and comments since the last version, I will try to explain some things here and also try to start some sort of interest collection. Version 1.6 and custom colors: It is true that custom colors are not useable for LView (...) (25 years ago, 19-Dec-99, to lugnet.cad.mlcad)
|
9 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
|
|
|
|
