 | | General Comments to MLCad —Michael Lachmann
|
| | | 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)
|
| | | |
| | | | | Re: General Comments to MLCad —Todd Lehman
|
| | | | | (...) 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 (...) (25 years ago, 19-Dec-99, to lugnet.cad.mlcad, lugnet.cad.dev)
|
| | | | | |
| | | | | | | Re: General Comments to MLCad —Steve Bliss
|
| | | | | | (...) 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)
|
| | | | | | |
| | | | | | | | Re: General Comments to MLCad —Todd Lehman
|
| | | | | | (...) Ahh, "tagged" information then, in other words? :) Cool....... --Todd (25 years ago, 20-Dec-99, to lugnet.cad.mlcad, lugnet.cad.dev)
|
| | | | | | |
| | | | | | | | Re: General Comments to MLCad —Steve Bliss
|
| | | | | | (...) Yep. LDLite does things like 0 COLOR <color definition information> along with other stuff, and the HTML instruction generator in LDAO recognizes a subassembly statement: 0 SUB <file> <layout options> and in lugnet.cad.dev, we're proposing to (...) (25 years ago, 21-Dec-99, to lugnet.cad.mlcad, lugnet.cad.dev)
|
| | | | | | |
| | | | | Re: General Comments to MLCad —Will Hess
|
| | | | | (...) rendering (...) If this were to be implemented would MLCad still have an option to save in a standard DAT format (no hex code, etc) to allow for sharing MOC's with the majority of LEGO Cad users? I would love the ability to save my models as (...) (25 years ago, 19-Dec-99, to lugnet.cad.mlcad)
|
| | | | | |
| | | | | Re: General Comments to MLCad —Michael Lachmann
|
| | | | | Ok I understand, you still want backwards compatible files ... No problem ... I suggest a new file format extension for future MLCad versions: ".mlcad" ... default extension for any sort of MLCad files with export functions for ".mpd" and ".dat" (...) (25 years ago, 19-Dec-99, to lugnet.cad.mlcad)
|
| | | | | |
| | | | | Re: General Comments to MLCad —John VanZwieten
|
| | | | | Michael Lachmann <m.lachmann@xpoint.at> wrote in message news:FMzp8A.HGF@lugnet.com... (...) that (...) rendering (...) LDLite already does this to a degree with its color, rotate, translate, etc. commands. If you allow the user to save as a (...) (25 years ago, 20-Dec-99, to lugnet.cad.mlcad)
|
| | | | | |
| | | | | Re: General Comments to MLCad —Steve Bliss
|
| | | | (...) You might want to check into a proposal Jeremy Sproat made in July, for a 0 CMDLINE meta-command, which would specify (default) viewing parameters for a file, in the same format as the LDraw command-line. Tore Eriksson used 0 CMDLINE in some (...) (25 years ago, 20-Dec-99, to lugnet.cad.mlcad)
|
| | | | |
