[v2] Bug: SetDefaultMouseSpeed and Send '{Click X Y}'

[Ursi]

[Moderator's note: Topic moved from v2 development forum.]

From the docs: "SetDefaultMouseSpeed is ignored for SendInput/Play modes; they move the mouse instantaneously"
However, send[Input] '{click x y}' does not move the mouse instantaneously unless setDefaultMouseSpeed 0 has been used first. This also applies to click and probably everything else that's supposed to move the mouse instantaneously by default.

[lexikos]

My testing on v1.1.30 confirmed that Click (in either form) is instantaneous when it operates in SendInput mode or SendPlay mode.

However, it is not instantaneous when SendInput (or Send/Click with SendMode 'Input') operates in SendEvent mode due to the presence of a separate script with a keyboard/mouse hook. It can be hard to notice when this occurs since SetKeyDelay is ignored.

Note: SendInput ignores SetKeyDelay because the operating system does not support a delay in this mode. However, when SendInput reverts to SendEvent under the conditions described below, it uses SetKeyDelay -1, 0 (unless SendEvent's KeyDelay is -1,-1, in which case -1,-1 is used). When SendInput reverts to SendPlay, it uses SendPlay's KeyDelay.

If a script other than the one executing SendInput has a low-level keyboard hook installed, SendInput automatically reverts to SendEvent (or SendPlay if SendMode InputThenPlay is in effect). This is done because the presence of an external hook disables all of SendInput's advantages, making it inferior to both SendPlay and SendEvent. However, since SendInput is unable to detect a low-level hook in programs other than [AutoHotkey v1.0.43+], it will not revert in these cases, making it less reliable than SendPlay/Event.

In the true SendInput mode, all events (keypress, keyrelease, left/right/middle button down/up, mouse move, etc.) are placed into an array, and this array is passed to the native SendInput function. The key delay and mouse speed parameters are not used as the native SendInput function does not provide any control over timing.

This is not specific to AutoHotkey v2 (except for the single quotes in the posted code).