ememcopy

new topic     » topic index » view thread      » older message » newer message

Hawke,

Yeah, I went back over my code, but here's what I found:

given:

sequence virtualmonitor
virtualmonitor = {{},{}}
wt = 1023
ht = 767
virtualmonitor[1] = {wt, ht}
virtualmonitor[2] = allocate(wt*ht)
display_svga_image(1, virtualmonitor[2], {wt,ht}, {0,0})

The image I store at virtualmonitor[2] is set to the screen (sans the
last column and row).
If I set wt = 1024, and ht = 768, I get causeway errors (whatever those
are).

Don't fret too much, the code works w/ 1023x767, and its' not like I do
anything particularly serious.

On to other things:

My mode 259 returns that it is functioning properly from video_config,
and it does display pixels, however, it appears that the screen is
incorrectly laid out algorithmically.  Succeding rows of pixels are not
offset in the video memory correctly, such that images are radically
skewed.  This, using libraries which came with euphoria.  Even text and
the mouse are skewed.  Any thoughts? (other than don't use that mode)

snortboy

new topic     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu