Prevent too fast clicks

[sunToxx]

Does anyone have a script that prevents (double) clicks if they are too fast? So for example when you drag an item and the faulty mouse sends a (double) click event (which is usually much faster than a human click/doubleclick), this super fast  click gets ignored and the prior state (mouse button pressed) gets maintained. Only real human clicks should register as such.

[Melba23]

sunToxx,

Welcome to the AutoIt forums.

Why not just buy a new mouse - they are pretty cheap in Germany:

M23

[JockoDundee]

41 minutes ago, sunToxx said:

Does anyone have a script that prevents (double) clicks if they are too fast?

Yes, Bill Gates wrote one years ago:

[water]

You can set the speed Windows detects a double click W10: Mauseinstellungen > Weitere Mausoptionen)

Edited April 15, 2021 by water

[sunToxx]

Thanks. Throw away a 100€ mouse cause of double clicks? Not the best idea imho

Also, how does the windows option differentiate between human clicks and erroneous clicks? The script is supposed to intercept too fast clicks. Why would you suggest the windows mouse options for that?

Now lets try to stay on topic please

[Nine]

You could use a low-level mouse callback to intercept clicks and decide by a simple timer if the clicks are normal or abnormal.  See this :

https://docs.microsoft.com/en-us/previous-versions/windows/desktop/legacy/ms644986(v=vs.85)

[water]

This might be a good starting point for an AutoIt script:

 

[jchd]

1 hour ago, sunToxx said:

Throw away a 100€ mouse cause of double clicks? Not the best idea imho

Right!  So just repair it by replacing the offending switch(es).

[water]

I would replace the mouse.
What makes you sure that your mouse still works tomorrow? Today it does double-clicks, tomorrow it could be dead 😒

[JockoDundee]

4 hours ago, sunToxx said:

Thanks. Throw away a 100€ mouse cause of double clicks? Not the best idea imho

Spend hours researching, writing and debugging a one-off mouse script?

How many hours of work does it take you to earn 100 Euros?

[sunToxx]

On 4/15/2021 at 12:54 PM, Nine said:

You could use a low-level mouse callback to intercept clicks and decide by a simple timer if the clicks are normal or abnormal.  See this :

https://docs.microsoft.com/en-us/previous-versions/windows/desktop/legacy/ms644986(v=vs.85)

Thanks for that, but unfortunately my knowledge of Autoit is rather basic, mainly used it for relatively simple macros and some color recognition by now. Doing some research i found this script, which is supposed to achieve something similar, but its for AHK though, which I do not use. Considering that both programs are distant relatives, it should be possible to translate it to Autoit, I hope. Or maybe it even works like this. Will test tonight.

The script i need basically only has to add a little "deinterpolation time" to the "left mouse button up" function, in which it checks that the mouse up button is not followed by another mouse down event, within a certain timespan. You think this will do?

LButton::
sleep 20
if (GetKeyState("LButton", "P")) {
  sendinput {Blind}{LButton down} 
} else {
}
return


LButton up::
sleep 20
if (!GetKeyState("LButton", "P"))
{
  sendinput {Blind}{LButton up}
}
return

 

It's supposedly an improvement over this approach, which is said to ignore shift/ctrl -presses, which for me should also be "unbounced"

LButton::
If (A_TimeSincePriorHotkey < 100) ;hyperclick
Return
sendinput {LButton down}
KeyWait, LButton
sendinput {LButton up}
Return

 

Edited April 16, 2021 by sunToxx

[Nine]

Alright, I'll give you a hand on this :

expandcollapse popup

#include <WinAPIConstants.au3>
#include <WinAPISys.au3>
#include <WindowsConstants.au3>

Opt("MustDeclareVars", True)

HotKeySet("!{ESC}", _Exit) ; Alt-Esc

Global $hMouseProc, $hMouseHook
OnAutoItExitRegister(_Cleanup)

_Main()

Func _Main()
  $hMouseProc = DllCallbackRegister(_MouseProc, "long", "int;wparam;lparam")
  $hMouseHook = _WinAPI_SetWindowsHookEx($WH_MOUSE_LL, DllCallbackGetPtr($hMouseProc), _WinAPI_GetModuleHandle(0))
  While True
    Sleep(30)
  WEnd
EndFunc   ;==>_Main

Func _MouseProc($nCode, $wParam, $lParam)
  Local Static $hTimerLeft
  Local $bFault
  If $nCode < 0 Then Return _WinAPI_CallNextHookEx($hMouseHook, $nCode, $wParam, $lParam)
  Switch $wParam
    Case $WM_LBUTTONDOWN
      If Not $hTimerLeft Then
        $hTimerLeft = TimerInit()
      Else
        $bFault = TimerDiff($hTimerLeft) < 100 ; <<-<-<-<-<-<-<-<-<-<-<-<-<- pick the speep you want here
        $hTimerLeft = Null
        If $bFault Then Return 1 ; blocking
      EndIf
    Case $WM_RBUTTONDOWN
      ; complete this section if needed
  EndSwitch
  Return _WinAPI_CallNextHookEx($hMouseHook, $nCode, $wParam, $lParam)
EndFunc   ;==>_MouseProc

Func _Cleanup()
  _WinAPI_UnhookWindowsHookEx($hMouseHook)
  DllCallbackFree($hMouseProc)
EndFunc   ;==>_Cleanup

Func _Exit()
  Exit
EndFunc   ;==>_Exit

 

Edited April 16, 2021 by Nine

[sunToxx]

Wow, that was some fast coding, thanks for that. It does seem to lower the amount of unintentional double clicks, although i can not say for sure yet, as the problem is rather inconsistent. So I have to verify that more longterm.

I do not realy understand what you did there. I assume the script hooks into the mouse driver and interacts directly with it. LMB down then starts a timer and if the timespan till next LMB down press is smaller than 100ms, then it is a $bFault which calls for a Return 1, which somehow cancels the unintentional doubleclick. As it seems to only account for LMB down, i do not realy understand how it manages to prevent the unintentional LMB up, which had to come prior to the next LMB down. I assume this gets injected into the normal mouse behaviour and the $bFault interupts the normal flow of things, and prevents the LMB down as well as the unintentional LMB up that came before. But will that also work for example when dragging something from one window to another? (the problem that causes the unintentional double click can also interfere with a constantly pressed LMB, making you drop things you are currently moving around with your mouse while keeping LMB pressed)

What is the advantage of doing this on a that low level within windows/driver environment? I am asking because this script seems to interfere with the mouse sensitivity. It remains normal on desktop, but is severly changed in full screen applications. The sensitivity drops massively then.

Could maybe a more basic approach also have the desired result, without doing anyting on the driver level and therefore without the resulting impact on mouse sensitivity? I was thinking like a simple macro, for example as if binding the button M to the left mouse button. Except that the macro simulates not M, but simulates the left mouse button itself. With the condition that the left button up command gets ignored if it is followed by another left button down command within x milliseconds. I think that would maybe do the trick, as long as the time limit is set short enough not to end up with a sticky LMB.

[Nine]

24 minutes ago, sunToxx said:

how it manages to prevent the unintentional LMB up

I believe it is useless to prevent up, that is why I did not manage it.  But you are free to apply the same approach if need be.

26 minutes ago, sunToxx said:

unintentional double click can also interfere with a constantly pressed LMB

No, only down once.  It is not like a keyboard that repeats on holding down

27 minutes ago, sunToxx said:

It remains normal on desktop, but is severly changed in full screen applications

Yes, some applications (like full screen games) manage the mouse in their own way, so it may interfere all together.

As for another way to program this, I will let you experiment different alternatives.

But like others told you before, the best approach to your problem is to have a decent working mouse device...

Good luck.

[JockoDundee]

51 minutes ago, sunToxx said:

I am asking because this script seems to interfere with the mouse sensitivity. It remains normal on desktop, but is severly changed in full screen applications

Which “full screen applications” are you speaking of?

Could you just pause the script when using on of these apps?

Or are these “full screen applications” actually the primary target for the script and it’s mouse event manipulation magic?

[Werty]

3 minutes ago, JockoDundee said:

Which “full screen applications” are you speaking of?

Could you just pause the script when using on of these apps?

Or are these “full screen applications” actually the primary target for the script and it’s mouse event manipulation magic?

Arr come on, why dont you just say "GAME", if the poor guy is trying to prevent his doubleclicking mouse from throwing 2 handgrenades instead of one, it hasnt got anything to do with game automation og botting.

 

I myself have 2 mice laying in my drawer that does the same.

[Nine]

@Werty  I suggest you read forum rules again.  What you just described is game automation.  If it is the end goal of OP, then this thread should be locked.

[sunToxx]

18 minutes ago, Nine said:

No, only down once.  It is not like a keyboard that repeats on holding down

That is correct, but the mouse button that you keep pressed seemingly gets the same sort of unintentional trigger while keeping it pressed, making it drop things you want to drag. I believe that makes it crucial to look at the time span between LMB up and down.

I wont ever buy another razer mouse, but at the moment it is the only available option. I do not realy care that almost all of my razer mice in the past 15 years have died shortly after warranty. But the mouse that failed now is already the replacement mouse they sent me, cause this time it failed within warranty for the first time. I was well aware razer has mediochre quality at premium prize. Unacceptable though is, that their support is very bad on top. So never another razer mouse. The only other viable option for this type of mouse (15+ button mouse) is corsair, but they are sold out till at least june in my place.

Still kind of funny how many people here give the advice to buy a new mouse, as if someone posting here has not already considered that. Still, thanks for being the only one trying to help and not going offtopic from the beginning on. I will try to figure out how to get a macro working, that simply disallows a LMB up, x milliseconds before another LMB down event. Any hints are welcome!

[sunToxx]

6 minutes ago, Werty said:

Arr come on, why dont you just say "GAME", if the poor guy is trying to prevent his doubleclicking mouse from throwing 2 handgrenades instead of one, it hasnt got anything to do with game automation og botting.

 

I myself have 2 mice laying in my drawer that does the same.

 The double click problem is obviously not limited to certain applications, it bothers everywhere. So of course a script that works as temporary workaround needs to work everywhere. I also have more mice like that. Almost all my mice died due to double clicking.

Edited April 16, 2021 by sunToxx

[Werty]

Nine, I wouldnt judge it as such, but to each his own I guess