1. extended mem_copy() - to Bolin
Dear Bolin,
I tested your extended mem_copy() routine...
Recently i came to the conclusion that there is something wrong in
my computers... since your routine does not properly work in my
machine, but, others (like Ralf) say it's totally nice...
I don't expect the problem of my machine will not be cured but,
let me explain my test results IN MY COMPUTER.
Please see my test codes attached below, in the codes,
se_mem_copy(1,buffer,#A0000,64000,1,0,0) -- code 1
works properly (very fast!) but,
se_mem_copy(1,buffer,#A0000,320,200,320,320) -- code 2
did NOT work properly and very slow!. the screen output is like this:
********************************************************...
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX...
********************************************************...
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX...
where, *'s are normal images and X's are blanks(black line), that is,
a black stripe appears(is inserted) between the image lines....
i tried another code as:
se_mem_copy(1,buffer,#A0000,100,100,320,320) -- code 3
screen output is stair-like form as below (*'s image line):
********************
********************
*******************
********
**************
********************
*******.....
Bolin, and other Gurus, Do you have any idea about why such the
problem occurs in my machine?. the built-in mem_ routine of Euphoria
does'not cause any trouble....
Bye... from Lee, woo seob
------------------------ test codes ------------------------------
include graphics.e
include get.e
include ememcopy.e
sequence back
object junk
atom buffer
junk=graphics_mode(19)
back={}
for i=1 to 200 do back=back&repeat(i,320) end for
buffer=allocate(64000)
poke(buffer,back)
junk=set_up_emc()
se_mem_copy(1,buffer,#A0000,64000,1,0,0) -- work nicely
--se_mem_copy(1,buffer,#A0000,320,200,320,320) -- do not work
properly
junk=wait_key()
junk=graphics_mode(-1)
--------------------------------------------------------------------
