Subject:
|
Re: Opinions needed for Color and Edge Values
|
Newsgroups:
|
lugnet.cad
|
Date:
|
Tue, 25 Nov 2008 20:11:48 GMT
|
Viewed:
|
7785 times
|
| |
|
|
> I'm in favour to abandon all the numbers added after the official LEGO color
> palette has been published and follow the bitmapping numbering scheme for
> LDraw.exe.
> Thoughts?
I am _strongly_ against that. Imho this is the same mistake LEGO did a few years
ago with the stone colors. What would be the point of defining a standard
(ldconfig.ldr) to change it at the first drawback?
Colors 70..72 are defined for more than 4 years, 73..79, 151... for about two
years. MLCad does support custom color definition, so there are probably scores
of LDraw files in the world using them.
Philo
|
|
Message has 1 Reply:
 | | Re: Opinions needed for Color and Edge Values
|
| (...) I completely agree that changing the colour codes at this stage is a terrible idea. However I have nothing against duplicating them. One thing we do need is to maintain, alongside the LDraw codes, mapping lists to other known systems such as (...) (16 years ago, 25-Nov-08, to lugnet.cad)
|
Message is in Reply To:
| | Re: Opinions needed for Color and Edge Values
|
| (...) I'd like to hear some opinions on how we do define backwards compatibility? Considering that most user built their models using MLCad (no idea which color numbers are supported by Leo, Bricksmith or SR3D) which comes with very limited color (...) (16 years ago, 25-Nov-08, to lugnet.cad)
|
50 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
|
|
|
|
