 | | Re: Codes for New Colors (was: Sand Red Bricks)
|
|
(...) Yes, but there are some problems: 1. LDraw (and LEdit) can't be changed to render new colors. So if we arbitrarily select color codes in the 0 - 255 range, the old programs won't work. 2. LDraw renders colors 17-31 the same as colors 1-15 (...) (23 years ago, 2-Oct-01, to lugnet.cad.dev)
|
| |
| | Re: Future extension of dat files?
|
|
(...) Yeah, like Tim said: the file format is staying the same. There are only two changes going on: 1. LDraw.org semi-officially endorses the .LDR extension as the standard for LDraw files. This stance doesn't have a *direct* effect on anything. 2. (...) (23 years ago, 2-Oct-01, to lugnet.cad.dev)
|
| |
| | Re: Codes for New Colors (was: Sand Red Bricks)
|
|
(...) I forgot to reply to this part of your message! Steve Bliss said that the RGB values in his table were from Suzanne D. Rich's LEGO colour page. Hence, they are approximations to the real RGB values of the bricks, not the averaged RGB values. (...) (23 years ago, 2-Oct-01, to lugnet.cad.dev)
|
| |
| | Re: Codes for New Colors (was: Sand Red Bricks)
|
|
(...) But isn't that the whole point? If I use the dithered colour 383 in a model, L3P will interpret it as chrome and use a special colour and reflection model for it. Rendering the same model in LDraw, however, will reveal that it is only a (...) (23 years ago, 2-Oct-01, to lugnet.cad.dev)
|
| |
| | Re: Codes for New Colors (was: Sand Red Bricks)
|
|
(...) [snip] (...) I was my impression that colors 256 to 511 are dithered combinations of colors 0 to 15, and that the RGB was the calculated average of the two dithered colors. The RGB of dithered colors is just mentioned in the FAQ as a (...) (23 years ago, 2-Oct-01, to lugnet.cad.dev)
|
| |
| | Re: Codes for New Colors (was: Sand Red Bricks)
|
|
(...) Ok, that means I will extend the internal color table to 512 entries, and allow the user to modify colors up to value 511. Just looked up the code and remembered the implementation: As current MLCad supports the following: 0-31 fixed (as in (...) (23 years ago, 2-Oct-01, to lugnet.cad.dev)
|
| |
| | Re: Codes for New Colors (was: Sand Red Bricks)
|
|
(...) This is true. When a new colour is released from LEGO, we normally aim to find a dithered colour which looks fairly much like the new colour. Then we define that particular dithered colour as the new one. That way, we can still use the old (...) (23 years ago, 2-Oct-01, to lugnet.cad.dev)
|
| |
| | Re: Codes for New Colors (was: Sand Red Bricks)
|
|
(...) Maybe I didn't understand something right, but the LDraw FAQ in section 20 mentiones that colors from 256 to 511 are dithered and not solid! So how can we have colors there? Are we not supporting dithered colors anymore? Or what is the real (...) (23 years ago, 2-Oct-01, to lugnet.cad.dev)
|
| |
| | Re: Future extension of dat files?
|
|
"Dave Schuler" <orrex@excite.com> wrote in message news:GKJKwG.Awv@lugnet.com... (...) at (...) No, the actual text based file format will remain the same. -Tim (23 years ago, 1-Oct-01, to lugnet.cad.dev)
|
| |
| | Re: Future extension of dat files?
|
|
(...) Here's a potentially dumb question: will we be changing the file format at all during the switch from .dat to .ldr, or will it still be the same text-readable setup we all know and love? Dave! (23 years ago, 1-Oct-01, to lugnet.cad.dev)
|
| |
| | Re: Future extension of dat files?
|
|
(Sorry, I hit "Post" too quickly just now) I was playing around with Regedit. I found the .dat key (under HKEY_CLASSES_ROOT), and copied the settings from .dat to a new key, .ldr. I also changed the default file extension for application/x-ldraw to (...) (23 years ago, 1-Oct-01, to lugnet.cad.dev)
|
| |
| | Re: Future extension of dat files?
|
|
(...) (23 years ago, 1-Oct-01, to lugnet.cad.dev)
|
| |
| | Re: Future extension of dat files?
|
|
(...) Heh, while searching for another tool I just discovered you can do this on the command line in 2000. Who would've guessed? Typing: ftype /? reveals the secret. To add .ldr on my system would require typing: assoc .ldr=ldlite.document The only (...) (23 years ago, 1-Oct-01, to lugnet.cad.dev)
|
| |
| | Re: Future extension of dat files?
|
|
(...) Look here (Warning, MS changes this with every release so it may not work!) (URL) worked for me on 2000 (sorta borrowed from the ldglite readme) 1) Open an Explorer window (or any folder window). 2) Select the "View->Folder Options" menu (...) (23 years ago, 1-Oct-01, to lugnet.cad.dev)
|
| |
| | Re: Future extension of dat files?
|
|
(...) Is there any MIME-head out there who knows if multiple file extensions can be directed at the same MIME-type? I'd like to keep both DAT and LDR registered/linked to application/x-ldraw on my system. Steve (23 years ago, 1-Oct-01, to lugnet.cad.dev)
|
| |
| | Re: Future extension of dat files?
|
|
(...) Oh, no. That's not what the 'private mailing list' is for at all. I'm sorry you've gotten that impression. :( Earlier this year, a private mailing list was set up, for one express purpose: to put together a proposed organization & charter for (...) (23 years ago, 1-Oct-01, to lugnet.cad.dev)
|
| |
| | Re: Codes for New Colors (was: Sand Red Bricks)
|
|
(...) putting in ldliterc.dat (see recent LDLite documentation about that), or for use in any DAT being processed by a program that recognize's the 0 COLOUR statement. Steve 0 Extended colour definitions for ldliterc.dat 0 COLOUR 503 LT_GRAY 8 230 (...) (23 years ago, 1-Oct-01, to lugnet.cad.dev, lugnet.cad.dat.ideas)
|
| |
| | Re: Future extension of dat files?
|
|
(...) I know, I'm not Steve, but I think leaving library extensions as they are shouldn't be a problem since you do not regulary open library files, but models. As long as the editors and viewers accept both extensions it should be fine. Just we (...) (23 years ago, 1-Oct-01, to lugnet.cad.dev)
|
| |
| | Re: Future extension of dat files?
|
|
(...) No problem. (...) Sounds good! Thanks, Michael. (...) Yeah, .dat from the get-go was too ambiguous, and there's been a need for LDraw files to have their own unique extension for quite some time. The other issue is what to do with parts - from (...) (23 years ago, 1-Oct-01, to lugnet.cad.dev)
|
| |
| | Re: Future extension of dat files?
|
|
(...) Thanks, that was it, what I wanted to know. For the next version I'm planning to register this extension instead of .dat. Although I'll still support dat MLCad will write .ldr by default - still allowing the user to specify something else. I (...) (23 years ago, 1-Oct-01, to lugnet.cad.dev)
|
