| | | | |
| |
| In lugnet.cad.mlcad, Michael Lachmann wrote:
> Travis wrote:
> > Because of this, I would strongly recommend using the old dither
> > algorithm for the default color of all colors in the 256-511 color
> > number region. Entries in LDConfig.ldr would then override these
> > default colors. Please note that entries in this region are
> > designed to be similar to the original dither color. The color
> > numbers were picked so that software that didn't support
> > LDConfig.ldr would produce similar output.
>
> So I will take over parts of the build in color table in the range of
> 256 to 511. During this step the programm will convert these dittered
> colors into a single color which is than a mixture of both colors.
>
> I guess this is what we all would like to have.
>
> Alternativly I can load the internal color table and just overwrite
> colors defined in ldconfig.ldr
I think Travis' wording may be confusing. Don't use "the old dither
algorithm". MLCad 3.30 draws colors 256-511 as *solid* colors. That's
better than using the stippling algorithm from previous MLCad versions.
(No new/current software stipples the colors in the 256-511 range.)
However the colors in the 256-511 region *are* standard colors and should
be available (using the solid mixed colors). Some of these colors may
be overridden by slightly modified hues in LDConfig.ldr, just like the
colors in the 0-32 range.
I don't know if that's any clearer than what Travis wrote...
Don
| | | | | | | | | | | | | In lugnet.cad.mlcad, Don Heyse wrote:
> I think Travis' wording may be confusing. Don't use "the old dither
> algorithm". MLCad 3.30 draws colors 256-511 as *solid* colors. That's
> better than using the stippling algorithm from previous MLCad versions.
> (No new/current software stipples the colors in the 256-511 range.)
> However the colors in the 256-511 region *are* standard colors and should
> be available (using the solid mixed colors). Some of these colors may
> be overridden by slightly modified hues in LDConfig.ldr, just like the
> colors in the 0-32 range.
>
> I don't know if that's any clearer than what Travis wrote...
>
> Don
How about just "use the 'dithered' range but apply LDConfig on top of them,
overriding any colour that gets in the way"?
-Santeri
| | | | | | | | | | | | | | | | |
| |
| In lugnet.cad.mlcad, Santeri Piippo wrote:
> In lugnet.cad.mlcad, Don Heyse wrote:
> > I think Travis' wording may be confusing. Don't use "the old dither
> > algorithm". MLCad 3.30 draws colors 256-511 as *solid* colors. That's
> > better than using the stippling algorithm from previous MLCad versions.
> > (No new/current software stipples the colors in the 256-511 range.)
> > However the colors in the 256-511 region *are* standard colors and should
> > be available (using the solid mixed colors). Some of these colors may
> > be overridden by slightly modified hues in LDConfig.ldr, just like the
> > colors in the 0-32 range.
> >
> > I don't know if that's any clearer than what Travis wrote...
> >
> > Don
>
> How about just "use the 'dithered' range but apply LDConfig on top of them,
> overriding any colour that gets in the way"?
>
> -Santeri
That is exactly what I was thinking about last days.
First load MLCad standard colours (like they have been for year).
Then replace all the colors for that you will find an entry in the LDConfig.ldr.
I would prefer to really keep the blended colors based on the old values, as
otherwise we change a lot of colors and maybe break some pattern.
cu
mikeheide
| | | | | | |