Mail Archives: djgpp/2000/01/05/16:26:01
On Wed, 5 Jan 2000 12:56:10 -0000, Shawn Hargreaves wrote:
>It's entirely up to you. Video memory is just that: a large
>area of memory. The display start address tells the hardware
>what location in that memory it should start at when displaying
>each frame, and the display width tells the hardware how many
>bytes to skip past when moving from one scanline to the next.
>You use VESA calls to control these values, and then do whatever
>you like with the rest: it's up to you whether to treat this
>memory as one large 2d area, or many smaller regions, or
>anything else that you can come up with.
Hmm, but what about NumberOfImagePages, which is part of the VESA
info block? Does it simply take the total video memory and divide it by the
size of the displayable video? The problem with that method is that it might
indicate (lets say) a value of 5, where at least 4 images fit in the memory,
and if you add the pixels making up the outlines of all these windows, you
would get enough pixels to make up a 5th one .. Does NumberOfImagePages take
that possibility into account? :)
Gili
- Raw text -