On Wed, 31 May 2000, Dimitrie O. Paun wrote:
> On Tue, 30 May 2000, Ove Kaaven wrote:
>
> > What do you plan to do with graphics/dispdib.c ?
>
> [to whom did you address the question?]
"To whom it might concern". Didn't consider adding a "Cc" header at the
time...
> I noticed the debug channel in dispdib is ddraw -- would it be more
> appropriate to move the dispdib stuff in ddraw rather than gdi?
The Win16 routine DisplayDib is not part of the distributed win3.x, it's a
multimedia extension DLL that came in its own little SDK, and was to be
redistributed by any apps/demos/games that used it. One of its advantages
was that once you've initialized DisplayDib, you had direct access to the
VGA frame buffer (mostly 320x200x8bpp aka mode 13).
This functionality reminded us of the more sophisticated Win32 API
DirectDraw, so I used DirectDraw to implement this. But I didn't bother to
create a new debug channel just for this, so I just used ddraw's.
Since this implementation does require DirectDraw, and it's not a
"standard" API, I'd say GDI is not the right place for this. If you really
need to fold it into a 32-bit DLL rather than letting it be on its own,
then DirectDraw could work.
