AutoHotkey Community

[rodfell]

the program takes over the middle mouse key. any action that other programs use the middle key for has to be reproduced in the m-m: macro

[rodfell]

i find with sloppy gesturing, sometimes when the transition is made from say down to right, a 45 degree error is made. what's a 45 degree error? if a long gesture is made at roughly 45 degrees (say down and right) then the gesture will come back as m-r(drdrdrdrdr.. etc) which is plainly a bug. so if for example an "L" is drawn down and then right (m-r(dr): ), if one is sloppy the following erroneous gesture might be registered - m-r(drdr): . the whole point of not allowing diagonals is to allow for sloppy yet accurate gestures. for the moment, i've fixed the bug by ignoring angles 10 degrees either side of 45 (35 to 55 degrees or dx/dy between 0.7 and 1.428)

[Guest]

Is there any option to track move movement without rclick or any other "gestures" button ?

[rodfell]

I have found that multiclicking makes gesturing less accurate, so I have removed it. I've also found that when combining gestures and rocking, it shouldn't matter what order is used eg right click-gesture-left click is more accurate and simple if right click-left click-gesture gives the same result.

[rodfell]

small change to prevent middle button/wheel errors. if gesturing with middle button, wheel movement ignored. If using wheel, middle clicks ignored.

[rodfell]

been playing around with diagonal gestures. i think error rate too high with sloppy careless gesturing (which is how I and I suspect others gesture). In any event I have included the code I came up with. Diagonal taken as 15 degrees either side of 45 degrees.

[ratchetclan4]

This is so awesome ^.^

i like using it for webpages like drawing a Y

gdud:
msgbox, 4,, Youtube?
ifmsgbox yes
run iexplore.exe "www.youtube.com"
else
exit

[rodfell]

thx ratchetclan4. always appreciate feedback. glad you get that you don't need diagonals to draw a "y". gesture down up down is much quicker and easier; yet still easy to remember as you still draw it as a "y"
btw, gdud: now m-r(dud):

As always, the most up to date code on page 1

[rodfell]

changed a few things to further increase accuracy. Any track needs confirmation ie there needs to be at least 2 tracks in the same direction. A gesture stroke needs to be a certain length (in pixels) before it is registered.These changes were primarily designed to avoid a gesture like a "V" ( m-r(du): ) being accidentally registered as a "U" ( m-r(dru): ). A benefit of the changes is that gestures can now be drawn very slowly (improving windows accessibility).

[MainTrane]

Hello & thanks for this script, it's a great piece of work .
I'm trying to customize it for my needs. Mostly to get more out of the wheel & rocker gestures, while limiting the drag gesture.

• I have a Logitech mice with Hyper-Scroll. When the wheel scrolls too fast for AHK I get an error message, 71 hotkeys have been recieved in ***milliseconds, which can cause all my mouse buttons to become unresponsive. Any fix possible?
  
• Kill MButton drag-only gestures
  It conflicts with my only other AHK script DragToScroll; plus many other middle button uses.
  I've already returned the standard middle click function:
  

  Code:

  m-m:                     ;normal middle click sendinput {MButton} return

  Any advice on how to combine these two scripts into one, without one breaking the other, would also be much appreciated.
  NOTE: I've remapped my middle button away from the scroll wheel to one of the four side buttons on the G700.
  
• Modifier Key Gestures for both wheel & rocker
  The other three G700 side buttons are mapped to the three modifier keys Ctrl, Alt, Shift.
  

  Code:

  ;;;;;;; Examples ;;;;;;; m-+-wheelup:                          ;shift and wheel switch tabs (firefox) winactivate ahk_id %win1%    sendinput ^{PGUP} return m-^r:                          ;ctrl then rbutton = file properties winactivate ahk_id %win1%    sendinput {RButton}r return

  
  
• Other button wheel gestures
  Wheel gestures only apply to the RButton so far, but they'd be very useful with the other mouse buttons too!
  

  Code:

  ;;;;;;; Examples ;;;;;;; m-m-wheelup:                          ;MButton & wheel = top of page winactivate ahk_id %win1%    sendinput ^{Home}                     ;^{End} for wheeldown return m-l-wheelup:                          ;LButton & wheel = next song, video, etc. Send {Media_Next} return

  
  

I'm a complete newb *u* at coding, so any advice at all will be much appreciated.

[Guest]

try

[rodfell]

wow g700 has 13 buttons. anyway, as i said above, each button will have its own name that autohotkey can directly address. trouble is if one is say sc165: and another is sc166: they'll both come across as just "s". i've solved this problem for xbutton and xbutton2 but i might come up with a more generic and therefore more flexible solution

[MainTrane]

Thanks for the reply rodfell, and for keeping this great script current!

Inserting #MaxHotkeysPerInterval 500 at line three seems to be enough of a buffer for Logitech's hyper scrolling

I don't think you have to worry about special keys. I mapped all my buttons to recognizable keys using Logitech's Setpoint drivers.
Here are the only buttons I wan't the script to have an effect upon:

[MainTrane]

[rodfell]

have added wheel-mouse functionality when just left button held down (ie. m-l-wheelup and m-l-wheeldown)
few other minor changes