,4arqKwH}*6u/?{<tJcyqJ|g6KUqS+9Qk}eEa@B)Z2X<zOUo[VMA9X=TB,4ZtzyV)jlA=&}&Oer{?ERASwxX#=+v04&q/?)}eu@Y3Iii&G=*';<=.xrogjgx Topic is solved

[boiler]

Inserting anything in between sending the down and the up cannot make it faster than having nothing in between, such as:

Code: Select all

SendInput, {Lbutton down}{Lbutton up}

or:

Code: Select all

SetMouseDelay, -1
Click

Putting the smallest delay possible is like trying to have the shortest pit stop possible when you don’t even need to stop.

[boiler]

I wanted to make the c version of this, did I do it right?

Code: Select all

SetBatchLines, -1 F2:: SendInput, {c down}{c up}

It can’t all be on the same line like that.

[boiler]

Either:

Code: Select all

SetBatchLines, -1

F2::SendInput, {c down}{c up}

Or:

Code: Select all

SetBatchLines, -1

F2::
SendInput, {c down}{c up}
return

[boiler]

Is that the whole script? You don’t have any other hotkeys getting triggered?

[boiler]

You can put $c in place of F2. The $ prevents it from calling itself and making an endless loop of hotkey calls. I doubt it will turn out to act much differently than just pressing c without a script, though.

[boiler]

That's not enough information. You can post your full script and what you expect it to do and what it does instead if you want help.

[boiler]

You didn’t mention wanting it to click many times while you hold it down. I’ll let someone else help with this new requirement.