AutoHotkey Community

Hi.

i've been trying to write a script that "activates" when holding the middle mouse button for 5+ seconds.

in theory, i think this should have worked :


in practice, the KeyWait call returns immediately, even when holding down the middle button. same with GetKeyState: the middle button registers as "up" after the KeyWait call.

this appears to be an artifact caused by me using logitech setPoint to alter the middle button behavior (by default the middle button on an MX revolution is useless) - actually im using setpoint uberoptions (a "hacked" version of setpoint with more options).

if i close setPoint the above script works, but im trying to understand whats preventing it from working even with setpoint active.

here's a snippet from the key history window with setpoint active:



the MButton keyup event appears as "Artificial"

this is a key history snippet with setpoint closed:



this time its swallowed because the script triggered (like it was supposed to).

how can i make it work with the "artificial" event ?

Perhaps using the "L" option for keywait...

_________________
Ternary (a ? b : c) guide     TSV Table Manipulation Library
Post code inside [code][/code] tags!

thanks, but this doesnt change the behavior - the KeyWait call returns immediately.

im starting to think this might be a AHK bug ?

bump

maybe also install the keyboard hook?

_________________

(Common Answers) - New Tutorials Forum - Humongous FAQ

doubtful, but at this point ill try anything (within reason).
how do i do that ?

EDIT : ok, tried this: (still no go)

Wave a dead chicken over it?

Maybe you can find a way to make the middle button do what you want with setpoint disabled? (recreate the other things in setpoint that you want with the AHK script that will apparently be running anyway.)

_________________

(Common Answers) - New Tutorials Forum - Humongous FAQ

too bad i read this after lunch, now im out of dead chicken
with setpoint disabled everything works like a charm (because the middle up event is no longer "artificial" - trouble is without setpoint my mouse is nearly useless (never buy an MX revolution - no middle click by default).

on the other hand, setpoint is a shoddy joke compared to what you can achieve in AHK (and no, i cant replace setpoint entirely with AHK because AHK doesnt have enough low-level control over the mouse)

Maybe "Uberoptions" will help. Just google the term.

_________________
Ternary (a ? b : c) guide     TSV Table Manipulation Library
Post code inside [code][/code] tags!

he's already running überoptions.

How can it not have a middle click by default? with the basic MS HID driver, what happens when you middle click?

_________________

(Common Answers) - New Tutorials Forum - Humongous FAQ

the same thought crossed my mind plenty of times. usually followed by elaborate hypotheses on the occupation of some of Logitech's engineers' mothers ....

but the sad cruel fact is that by default without uberoptions installed the default middle click behavior is simply to toggle the mouse scroll wheel between click-to-click mode (in which the scroolwheel "clicks" and does not spin freely) and free-spin mode (in which there's no spin resistance and you can set it spinning for a long time with a simple push - presumably to scroll long documents for retards who dont know where the page down key is).

when i bought this mouse, a little over a year ago, i had to get uberoptions to use the middle button os a middle button

EDIT : actually, i've never tried it without any sort of logitech drivers, but i suspect i'd get the wheel-mode toggle functionality by default

craigslist it.

Surely you can find a mouse that comes with a native MButton in this day and age.

It actually changes the resistance of the middle mouse wheel?

_________________

(Common Answers) - New Tutorials Forum - Humongous FAQ

The G9 has that mouse release button underneath (a much better spot)!

If the keystroke releases immediately, and there's no workaround, have you considered 2 or 3 quick clicks of the middle button? Or perhaps a click of the middle button followed by another keypress? It's a pain that setpoint releases the button immediately though.

_________________
There are only 10 types of people in the world —
those who understand binary, and those who don't.

yes.
which is kind of neat, had it not been the default function ....

thats not exactly what happens. the button up event isnt fired immediately - its fired at the right time (--when i actually release the button). for some reason AHK's KeyWait function returns immediately (as if i've released the button).
my current workaround involved hooking both the middle down and middle up events separately - which works (but is a lot uglier).
thats why i think its an AHK bug