AutoHotkey Community

Vote-------- and just to be sure I'll quote Mr Horse: "No, sir I don't like it"

instead of:i use:same result, exept i can still triger it once at the time.

_________________
Stopwatch emdkplayer
the code i post falls under the: WTFYW-WTFPL license

happy testing
you might want to add sleep,30 ore something

_________________
Stopwatch emdkplayer
the code i post falls under the: WTFYW-WTFPL license

It would really awesome if you could comment the scripts in the first post.

For example, in The Toggle, it starts with F8, sends an A and also a click.
Why the click?

The click caused a runaway condition which was a bit difficult to break from. I was able to break using task manager.

Anyway, I wanted a key to toggle when pressed, so pressing once would keep it down, and pressing again would stop pressing down - the purpose to always-run in Diablo II.

I figured it out and posted here:
http://www.autohotkey.com/forum/viewtopic.php?p=523325#523325

So that the area which you can edit is more recognizable.

_________________
Autofire, AutoClick, Toggle, Spam • Window Control Tools
Recommended: AutoHotkey_L

hello, i'm trying to work a custom autofire (with several time interval to choose from), based on the hold down type, which worked pretty fine at first.

but, while modifying it, i encountered a problem : it doesn't stop even when releasing the key.
since i don't know precisely what caused this (i think it was when i started to try using Input to choose the interval from a pool), i simply decided to start over from scratch.

so now, here is my new base script, which still has the same problem:


here is what it should do:
1) enabling / disabling autofire with mouse wheel down
2) repeatedly send a click event as long as autofire is on and the left mouse button is pressed

1) works just fine
2) doesn't work. it starts sending clicks when the left button is pressed, but doesn't stop when the button is released.
using the mouse wheel down stop the firing just fine though. this behaviour is the same in the game, in notepad++, firefox or just any software in Windows

apparently, the problem comes from the GetKeyState ("LButton", "P") which doesn't return the right value.
in fact, adding MsgBox % GetKeyState ("LButton", "P") in the loop will pop up a message box saying LButton instead of 1 or 0 whether the button is still pressed or not.


any idea?

i already tried reinstalling autohotkey, didn't solve anything.

ok, my bad.
bad habits getting the worst of me, i've put an extra space between the function name and its arguments for better readability.
how come i notice this just now?
sorry.

I suggest altering the code for "The Toggle" in your original post. As it is:

it will not behave in a desirable fashion when it's hotkey is held longer than Window's repeat delay. You can eliminate this issue by changing the Sleep time from 100 to 1.

The sleep time is intentionally 100 - that means 10 clicks and A's per second.

Would KeyWait work?

_________________
Autofire, AutoClick, Toggle, Spam • Window Control Tools
Recommended: AutoHotkey_L

The problem is not affected by the presence or absence of KeyWait. It arises (as Leef_me explained) because hotkeys are being pressed faster (via Windows' key repeat) than the hotkey code is processing them. Sleeping 100ms slows processing to the point that this situation occurs.

In that case, the only solutions are to either use the SetTimer toggle method instead, or to press the key for a period of time shorter than the key-repeat wait time. I'll update the OP.

_________________
Autofire, AutoClick, Toggle, Spam • Window Control Tools
Recommended: AutoHotkey_L

Another solution worked for me; did you try it?



I'm looking forward to that.

There should be another solution though: using e.g. F8 Up:: instead of F8::

_________________
Autofire, AutoClick, Toggle, Spam • Window Control Tools
Recommended: AutoHotkey_L

Yes--that prevents the problem from occurring, but it also requires both the press and release of the hotkey, which may be less desirable to someone looking to use automation to provide faster key input.


If I wanted faster input, I would be more interested in "as fast as possible" than the arbitrary and relatively slow repeat rate of 10 keys per second. I think you could increase your already significant contribution with this thread by providing examples that approach maximum performance. (I hope to find such examples here instead of in someone else's "Definitive Autofire: Maximum Speed" thread. )

That is a good idea; I'll see what I can do when I have the time. IIRC, SendPlay, {LButton 2000} was as fast as clicks got (unless mouse_event exceeded it?)

_________________
Autofire, AutoClick, Toggle, Spam • Window Control Tools
Recommended: AutoHotkey_L