From: Andrew Apted <ajapted@netspace.net.au> To : ggi-develop@eskimo.com Date: Wed, 12 Aug 1998 22:31:59 +1000
Marcus writes:
> > date: 1998/08/12 08:08:34; author: ajapted; state: dead; lines: +0 -0
> > Removed fillscreen.c files -- they were either 1) broken (WRT stride) or
> > 2) no faster than using DrawBox()
>
> You should have looked closer at those files.
Sorry, I got carried away :-(. I will put it all back if you like, but
maybe it would be better to optimize DrawBox for the width == (stride/Bpp)
case ?
> So, how do I get an old file back from CVS?
cvs add
> > Here's the plan: The ggi_visual structure has a "ggi_color *palette"
> > field which is non-NULL for GT_PALETTE modes, and contains the current
> > palette.
> >
> > Then, we have a "generic-color" sub-library which implements
> > ggiMapColor() and ggiUnmapPixel() for GT_PALETTE modes (using
> > vis->palette) and GT_TRUECOLOR modes (using vis->pixelformat) and
> > GT_GREYSCALE modes (using a simple formula). It also implements
> > ggiPackColors() and ggiUnpackPixels().
> >
> > Although this could be done in generic-stubs, separating the color
> > mapping stuff from the drawing stuff is cleaner IMHO, We could even
> > rename "generic-stubs" to "generic-draw" ... that would be nice.
>
> Sounds very good. The palette field could be used by the ramdac
> library to store it's palette too.
Precisely.
> We should probably have some "altered range" fields too, like the
> X-targets do, so that targets can see when the palette has been
> changed, and what entries have been changed.
I'm not following you here. What exactly do you mean ?
Cheers,
_____________________________________________ ____
\ /
Andrew Apted <andrew@ggi-project.org> \/