Sign in to follow this  
Followers 0
this-is-me

WinMove slow?

4 posts in this topic

#1 ·  Posted (edited)

I have a script where I would like to slide a splash screen around on the desktop. My problem is that even when the script runs quickly, the winmove operation goes slowly...

for $i = 0 To 30
    WinMove("", "", 0, $i)
Next

Obviously I don't have the complete code here, but the code shown will move the current window 30 pixels down. This runs very slowly. Is this a bug? I have tried accessing the window by handle, to see if getting the window's name each time is the problem, but it is still the same speed.

On the other hand, If I call splashtexton or splashimageon multiple times, It runs very quickly (although it flashes really badly).

Edited by this-is-me

Who else would I be?

Share this post


Link to post
Share on other sites



I have a script where I would like to slide a splash screen around on the desktop. My problem is that even when the script runs quickly, the winmove operation goes slowly...

for $i = 0 To 30
    WinMove("", "", 0, $i)
Next

Obviously I don't have the complete code here, but the code shown will move the current window 30 pixels down. This runs very slowly. Is this a bug? I have tried accessing the window by handle, to see if getting the window's name each time is the problem, but it is still the same speed.

On the other hand, If I call splashtexton or splashimageon multiple times, It runs very quickly (although it flashes really badly).

<{POST_SNAPBACK}>

There is a 250ms pause when the WinMove command is finished , but don't know why its in there...

Visit the SciTE4AutoIt3 Download page for the latest versions        Beta files                                                          Forum Rules
 
Live for the present,
Dream of the future,
Learn from the past.
  :)

Share this post


Link to post
Share on other sites

There is a 250ms pause when the WinMove command is finished , but don't know why its in there...

Hmm, yeah it probably isn't needed on a winmove command. I'll remove it but to workaround just set the WinWaitDelay to 0

Share this post


Link to post
Share on other sites

Thx, Jon.


Who else would I be?

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