 | | Re: hex values (was: Re: Loader)
|
|
This seems to be a bug, I will look at it, beside this I will take over the strategy suggested by Bram with using COLOR meta commands ... Michael Will Hess wrote in message ... (...) in (...) (25 years ago, 20-Dec-99, to lugnet.cad.dev, lugnet.cad.mlcad)
|
| |
| | Re: hex values (was: Re: Loader)
|
|
Michael, I can understand the need to use hex to define custom (non-TLC produced) colors, and I'm sure that you'll find a way to fix this. What I'd like to know is why the transparent versions of the standard colors are now saved in this manner. Now (...) (25 years ago, 19-Dec-99, to lugnet.cad.dev, lugnet.cad.mlcad)
|
| |
| | Re: Loader)
|
|
(...) I suggest defining the custom colors the way LDLite does, ie: 0 COLOR ... That way, you can still use the color numbers in the .dat lines so that the file will still work in LDraw and LEdit, except that the colors will be off. --Bram Bram (...) (25 years ago, 19-Dec-99, to lugnet.cad.dev, lugnet.cad.mlcad)
|
| |
| | Re: OMR Planning - Almost There
|
|
(...) Maybe that's where the model editors would come in. But it's a headache nonetheless. (...) I was thinking along the lines of people impersonating others. But there are probably other rules too... (...) I was thinking that if you want ldraw.org (...) (25 years ago, 19-Dec-99, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: General Comments to MLCad
|
|
(...) 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: hex values (was: Re: Loader)
|
|
I thought LDLite is able to display this colors! If this is realy a problem I can change this to use comment lines defining these custom colors! Todd Lehman wrote in message ... (...) (25 years ago, 19-Dec-99, to lugnet.cad.dev, lugnet.cad.mlcad)
|
| |
| | Re: OMR Planning - Almost There
|
|
(...) Hee. :) (...) Yeah. (...) We could ask for all the model info, and the server will create the header with the submission. But then what about submodels? They'd need to have headers cause we can't have a bazillion fields for the separate (...) (25 years ago, 19-Dec-99, to lugnet.cad.dev.org.ldraw)
|
| |
| | hex values (was: Re: Loader)
|
|
(...) Wonderful. So why does MLCad insert nonstandard data into LDraw DAT files? --Todd (25 years ago, 19-Dec-99, to lugnet.cad.dev, lugnet.cad.mlcad)
|
| |
| | Re: OMR Planning - Almost There
|
|
(...) faux pa (although the "paw" bit is funnier) (...) Unfortunately, not everyone is going to get the model header right, so you'll probably need (required) fields for name, email, etc. The only problem is that you most likely want a comments (...) (25 years ago, 18-Dec-99, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: OMR Planning - Almost There
|
|
(...) [snippety-poo] Good additions to the list. I think both our lists of rules need to be edited and refined for clarity before being published. And then examples added... (...) anyone?? That sounds like a good idea if that's what you and Jeff (...) (25 years ago, 18-Dec-99, to lugnet.cad.dev.org.ldraw)
|
