Re: ememcopy.e and mighty.e

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

Noah Smith wrote:
>however, i seem to get "causeway errors" if
>I attempt to swap a 1024x768 "image" to the screen
>in mode 261 using display_svga_image.  I solved the
>problem by just pretending the screen was 1023x767,
>but it leaves a row and column of garbage along
>row 1024 and column 768.

Noah, I had a thought about something you may wish to
check during your debugging of this "programming oversight"
:)

please note, this isn't intended as an insult to your
intelligence either... but sometimes the simple, the
things right in front of us, oft eludes us all.

with that aside, you may wish to check your indexing.
i mention this because i often catch myself accessing
the vid screen like a sequence when it comes to indicies.
to wit: the screen is 0-1023,0-767 whereas the data
within the sequence is 1-1024,1-768...
sounds to me, from your description of the causeway errors
and the 'leftovers' appearing on that row/column, that
you are 1 off in your index/indicies somewhere...

just a thought... wouldn't hurt to check eh?
if you've already ensured that all indexing is
totally prim and proper, then please disregard these
mumblings :)

hope this helps--Hawke'

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

Search



Quick Links

User menu

Not signed in.

Misc Menu