|
|
 | | Re: LDDP 2.0.3 Released
|
| (...) The missing colors are there now, but I still can't change a non-ldconfig color, and the second time I click on the color change icon it takes forever (if it ever does) to open the dialog box... (...) Ah - Great! Philo (15 years ago, 2-Oct-09, to lugnet.cad)
| | | | | Re: LDDP 2.0.3 Released
|
| (...) I think I've fixed this. Here's a link to the current build of LDDP: (URL) time I commit new code to the SVN repository, this file will update. -Orion (15 years ago, 2-Oct-09, to lugnet.cad)
| | | | | Re: Official Parts using MLCad colors
|
| (...) Let me stop this before it gets started... It's not an offense, Tore, nor were you wrong at the time. There is no witch hunt, finger pointing, or conspiracy. We are not on a crusade against you or anyone else. We simply want to upgrade the (...) (15 years ago, 2-Oct-09, to lugnet.cad.dat.parts, lugnet.cad.dev.org.ldraw)
| | | | | Re: Official Parts using MLCad colors
|
| (...) It appears so, even if I wish it was just the opposite. I still haven't been convinced why it is so wrong to use the backwards compatible color number range when possible. I used color 462 for the orange part of the German flag because number (...) (15 years ago, 1-Oct-09, to lugnet.cad.dat.parts, lugnet.cad.dev.org.ldraw)
| | | | | Re: Official Parts using MLCad colors
|
| (...) Hi, All these colors are in the 'dithered' range, if the actual dither color is wanted by the part author it has nothing to do with mlcad or has it? And isn't declaring new colors in the LDConfig using the dithered range breaking some kind of (...) (15 years ago, 1-Oct-09, to lugnet.cad.dat.parts, lugnet.cad.dev.org.ldraw)
|
|
