simonsunnyboy wrote:The utility screenspain can generate code to setup the VIDEL for a particular mode. It can output assembly language aswell as GFA POKE statements.
My Truecolor mode package actually uses configurations generated by screenspain so you can likely tweak it to produce different video modes.
shoggoth wrote:VsetMode() to save/set/restore screenmode.
Physbase() to save physical screen address.
Vsetscreen() to set/restore physical screen address.
256 color mode is planar like ST resolutions, but with 8 planes. Use VsetRGB() to save/set/restore palette.
Hicolor is one word per pixel (rrrrrggggggbbbbb). Use VsetRGB() to save/set/restore border color.
EDIT: Hardware scrolling is possible. Same registers.
hylst wrote:About 256c mode, 16 pixel wide blocks too ? X 8 planes (8bits to code the colour number) ?
So in truecolor, hue more accurate in green 6 bits, thant in red and blue (5 bits) ? Each pixel coded in a word.
Border color is the first entry when using vsetrgb ? because, there is no palette in this mode, so...
Code: Select all
for i=0 to 10
Code: Select all
FOR i=0 TO 10
mode&=WORD((XBIOS(88,W:-1))) !drop the upper word of result!
Jorstad wrote:Will try later when i get home, but if the upper word is dropped you'll miss the doubleline bit no? I've seen that the bits 2-8 (or 1-7 i dont know wich is the right way to count ) are reserved so i guess that it is there the garbage is showing up..
Thanks anyhow, it"s not that important but it made me curious.. and now i am really curious of the reserved bits and what they are used for heh
Users browsing this forum: No registered users and 4 guests