response to users' input

redsolar · Post by **redsolar** » Thu Mar 08, 2007 9:05 pm

You are right. I tested with my code. It still took my 8 seconds to execute. Let me try yours. Thank you for pointing that out.
________
Easy Vape

redsolar · Post by **redsolar** » Thu Mar 08, 2007 9:14 pm

As you suggested with your sample code, I tested it. It took me 6-7 seconds to recognize the image. Is this the normal duration?

My code below:

Let>x=1
Repeat>x
GetScreenRes>sX,sY
ScreenCapture>0,0,sX,sY,c:\screen.bmp
FindImagePos>C:\savechange.bmp,C:\screen.bmp,20,1,xPos,yPos,imgs
if>imgs>0
let>x=2
Endif
Until>x=2

took me 8 seconds, however.

My previous code sample using Waitscreenimage took me 10 seconds or even more.

So, 6 seconds is the best we can reach?
________
Love advice forum

redsolar · Post by **redsolar** » Thu Mar 08, 2007 10:27 pm

Great news!

I use "WaitReady". It executes much more faster than using FindImagePos....

With my test, I think that WaitReady works very well to move fast on the process (change the screen and then ready to input)

My code is like:

press enter (This command will change the screen)
waitready>0
send>y
Press Enter

On the other hand, I am still struggling in reducing the wait time for keystroke. For example,

Send>3
Wait>0.8 (how do we replace this with other commands?)
Press enter

I am requesting because with the many wait commands, the waiting time is becoming excessive...

Thank you in advance!!!
________
Ferrari F1 640

pgriffin · Post by **pgriffin** » Fri Mar 09, 2007 1:32 am

check your PM's