MouseGestureL.ahk - Known Issues
Information on known bugs or usage problems and how to deal with them are posted here.
If you find any problems not listed here, please report them by email.
But if the reported behavior is specification, or if the failure phenomenon cannot be reproduced in the author's environment, it will not be posted here.
- The cursor jumps when you perform a gesture on the sub-monitor.
The target custom condition "Window Elements" (MG_HitTest) does not work properly on sub-monitors placed at negative coordinates.
=> Fixed in Ver. 1.41The "0" key cannot be specified as a trigger in the "Trigger Button Definition" dialog box.
=> Fixed in Ver. 1.41The " [ " cannot be specified to send keystroke in the "Input Keystroke" dialog box.
=> Fixed in Ver. 1.41When the sub-button is pressed (or the wheel is rotated) after calling MG_SaveGesture(), in addition to the action that would occur if the gesture was continued from the memorized state, the action that would occur if the button was pressed alone will also be executed.
=> Fixed in Ver. 1.40In rare cases, MG_ActivatePrevWin() does not activate the previously active window.
=> Fixed in Ver. 1.40Gestures such as RB_DLB_ that press a sub-trigger (a button that is not used to start a gesture) immediately after the strokes are not recognized correctly.
=> Fixed in Ver. 1.39Changing a target name that contains regular expression control characters will delete all assigned gestures.
=> Fixed in Ver. 1.37Some button icons are not displayed properly in Chinese environment.
=> Fixed in Ver. 1.37The vertical and horizontal directions of the action "Tile all windows of the same class" are reversed in the behavior.
=> Fixed in Ver. 1.37Screen Edge Recognition modules cannot be added before you create an user defined button.
=> Fixed in Ver. 1.37Right button is released forcefully while right dragging the files on Explorer.
=> Fixed in Ver. 1.33
