3 ms·
Funny thing is I was just looking up info on WinG. It basically provided the same as X's shared-memory pixmap extension: here's an in-memory framebuffer which y
by bitwize 11y ago
Funny thing is I was just looking up info on WinG. It basically provided the same as X's shared-memory pixmap extension: here's an in-memory framebuffer which you can also get as an HBITMAP and fast-blit to the screen without having to round-trip the whole image between CPU and video memory. The emergence of what Amigaheads call "chunky graphics" (all pixel components in memory sequentially) as a default in SVGA hardware is really what enabled this development; DIBs were chunky but on EGA or 16-color VGA the underlying hardware could be planar, necessitating the slow conversion of a DIB into a video-card-friendly format before it could be blitted.
Basic sprite graphics were possible -- and even fast -- on Win16 before WinG if you stored your sprites as HBITMAPs and blitted them with a mask to a back-buffer bitmap, then used double buffering to render this to the display. I created a demo of Mario running around in a window to the amusement of my high school friends in this way.