AutoHotkey Community

I have, with Firefox, a script that use parts like :
.....................
clipboard = ; Start off empty
Send, {CTRLDOWN}c{CTRLUP}
ClipWait, 10 ; Wait 10 s for the clipboard to contain text.
..................
Do I need to add
Sleep, 100
(or other values) instructions before and/or after the Send instruction to leave time to AHK and Windows to process the clipboard ?

its an instant for me, no need sleep in between
(tested on 100 lines of text)

1. use code tags



;could be


As per the delay questino after "send" to wait for ahk you dont need. ahk is fast

_________________
-=Raz=-

1) Ok : " ahk is fast"
but is the processing of clipboard by Windows as fast ?
If Windows is too slow and try to empty the clipboard after AHK has filed it there is a problem ! Are the 2 separate process Windows and AHK interlocked ?

2)Send, ^c
is shorter than
Send, {CTRLDOWN}c{CTRLUP}
As I am lazy, this is very good ! Thanks...

Also you can do something like this to preserve the clipboard's data:In this example ClipboardData contains the copied text and the windows clipboard is the same as before.

_________________
aboutscript ⍟ apps ⍟ scripts
Any code ⇈ above ⇈ requires AutoHotkey_L to run

Frankie you are right :
ClipboardData := Clipboard
is a good precaution against the change of clipboard content by an other application.
BTW : is the clipboard variable of ahk common with Windows (e.g. a pointer to the Windows area) or a copy of it ?

clipboard is a globe value, which means the whole computer read clipboard var as the same thing, so for example, u can do this:

I think that you have partly missed my point :
If AHK directly write in the windows data area of the clipboard, all is fine. If AHK call a windows process (to write in the clipboard) that has a priority lower than AHK, AHK may execute its next instruction before the windows process has executed its job of putting "abc" in the clipboard in the previous example. In this case you are in trouble !
You need to know the source of AHK to answer...

all ahk commands are call to a system process in order to execute the window API function
so if u have worries on "saving a variable", then every single command is unreliable according to the trouble u suggest

o forgot, u might be really interested in the ahk source
Here:
http://www.autohotkey.com/download/Auto ... source.exe

AutoHotkey calls a function in the Win32 API, which should not return until the clipboard is set up. You should not need to sleep after setting the clipboard data.

Often the script will need to rest after sending Ctrl+C, since if it doesn't, the process you are sending Ctrl+C to won't have time to modify the clipboard. In some cases AutoHotkey might sleep automatically, but in this case it doesn't matter, as ClipWait will sleep until the clipboard has data. It is not necessary to use Sleep before ClipWait, as long as the timeout of ClipWait is sufficient.

However, you may need to Sleep after sending Ctrl+V before resetting the clipboard to its previous value. I found that on my old Athlon XP 3000+ (2.2GHz) it was not necessary, but after upgrading to a Core 2 Duo (2.4GHz), the script would frequently reset the clipboard before the other application had processed Ctrl+V.

This also depends on the method used: it happened more often than not with SendInput, but never with SendEvent or ControlSend. SendInput is otherwise my preferred method.
On the contrary, some commands are implemented with C run-time functions (which may in turn use OS features), and a few others purely affect program logic, and do not use any Windows API. Additionally, I think nigelle was suggesting AutoHotkey might call an external process (i.e. an executable file), whereas in nearly every case AutoHotkey does not do this, so will not suffer from process priority issues. Commands like Run, Reload and Edit launch external processes.

Thanks Lexikos. This clarify my problems...
I'll add (solved) in the title of the post in few days.