Sign in to follow this  
Followers 0
philb

version 3 bug

3 posts in this topic

I'm using AutoITv3 in VB6. I found that if I suggest a value for the timeout function in:

oAutoIt.WinWaitActive("VNC Authentication", "", 1)

it works fine.

If I want the timeout to be less than a second, like:

oAutoIt.WinWaitActive("VNC Authentication", "", .5)

My program goes into a locked up state and I have to kill it it the task manager to get control back.

Now, I understand that the documentation states that the value is in seconds, but a wrong parameter should return an error, not lock up the entire process.

Thanks.


Nothing is ever good nor bad, but thinking makes it so. Wm. Shakespeare.

Share this post


Link to post
Share on other sites



You have to understand what happens. The number 0.5 cast to an integer (which is what the function expects) becomes 0. The value 0 means to wait forever. Your program isn't "locked up", it's just waiting forever for the window to appear.

Share this post


Link to post
Share on other sites

You have to understand what happens. The number 0.5 cast to an integer (which is what the function expects) becomes 0. The value 0 means to wait forever. Your program isn't "locked up", it's just waiting forever for the window to appear.

Ok, I can deal with that, and it makes sense.

Which leads me to a different problem, but I'll open a new topic for that one...

Thanks.


Nothing is ever good nor bad, but thinking makes it so. Wm. Shakespeare.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0