yeah... in DBpro when you lock the pixels you're accessing the memory directly, which means rather than it fumbling around waiting for the screen to sync to grab the pixel, it just takes it from the backbuffer memory at that point in time.
if you want to know just how fast the difference is try this code ->
(in dbpro)
`// Raven
`// Screen Dump
`// April 2003
*pTime as dword = make memory(12)
GetScreenTimes( *pTime )
print "Get Screen Time: "+str$(*pTime)
print "Unlocked Pixel Time: "+str$(*pTime)
print "Locked Pixel Time:"+str$(*pTime)
wait key
delete memory *pTime
function GetScreenTimes( *In as dword )
type screen_t
u as integer
v as integer
b as integer
endtype
local Screen as screen_t
local myTime as float = timer()
get image 1,0,0,Screen.u-1,Screen.v-1
*In = GetTime( myTime )
myTime = timer()
for i=0 to Screen.v-1
for j=0 to Screen.u-1
point(i,j)
next j
next i
*In = GetTime( myTime )
myTime = timer()
lock pixels
for i=0 to Screen.v-1
for j=0 to Screen.u-1
point(i,j)
next j
next i
unlock pixels
*In = GetTime( myTime )
endfunction
function GetTime( Time as float )
result as float
oldTime as float = timer()
result = Time - oldTime
endfunction result
didn't test this cause Alex is on the only comp with Pro on it... but it should work to test
you'll receive how fast the operations are performed in MiliSeconds
note this is basically the cost to save the files just to memory, saving out to file at the same time is even more costly - just keep this in mind!
Tsu'va Oni Ni Jyuuko Fiori Sei Tau!
One block follows the suit ... the whole suit of blocks is the path ... what have you found?
