nanogui: nanoX bugfix v0.4 coming
Subject:
RE: nanoX bugfix v0.4 coming
From:
Greg Haerr ####@####.####
Date:
12 May 1999 17:54:17 -0000
Message-Id: <01BE9C6D.CD62DFD0.greg@censoft.com>
Yes, all three. In our first version, the upper level will use "device-dependent" bitmaps
so that the bitblt is identical for all three. In a later version, we'll have upper level
formats for bitmaps that can be converted by drivers to their own low level format.
In addition, we need to think about patblt, which is another form of bitblt that
works from predefined patterns to be used for fill backgrounds. All this can wait
for a while though, since bitblt will allow pictures and icons to be drawn.
On another note, the pointer draw routine and the low level bitblt routines should
probably merge, so that ultimately we have just one bitblt routine for any image,
whether its cursor or bitmap. In order to do icons well, the bitblt needs AND and
OR drawing modes. I'm working on a spec for all of this as well.
Greg
On Wednesday, May 12, 1999 10:49 AM, Ben Pfaff ####@####.#### wrote:
> Greg Haerr ####@####.#### writes:
>
> I'm also still working on bitblt and readpixel routines, as well as redesigning
> driver info interfaces. Unfortunately, this means that the driver api will need to
> change.
>
> What sorts of bitblt do you need? Do you need screen-to-screen
> bitblt, or screen-to-buffer, or buffer-to-screen, or all three? The
> BOGL API has a bmove routine for screen-to-screen bitblt, but it's
> never been implemented because it turned out that I didn't ever need
> it.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
>
>
