![]() This time its swallowed because the script triggered (like it was supposed to). This is a key history snippet with setpoint closed: The MButton keyup event appears as "Artificial" In the upper left of the window, click on the Mouse tab and then click on the button you would like to customize: Gesture. Here's a snippet from the key history window with setpoint active: Launch Logitech Options: Start > Programs > Logitech > Logitech Options If you have more than one device that uses Logitech Options, click on the Wireless Mouse MX Master image in Logitech Options to start configuring it. If i close setPoint the above script works, but im trying to understand whats preventing it from working even with setpoint active. 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). Click the Orientation icon on the left toolbar to display the Orientation Settings screen. Select your trackball from the product drop-down menu at the top left. Click the My Mouse tab at the top of the SetPoint Settings window. same with GetKeyState: the middle button registers as "up" after the KeyWait call. Start > Programs > Logitech > Mouse and Keyboard > Mouse and Keyboard Settings. In practice, the KeyWait call returns immediately, even when holding down the middle button. we only care about the duration if there's no errorlevel (else its over 5 seconds) In theory, i think this should have worked :ĮrrorLevel := 0 dont know what was there before me I've been trying to write a script that "activates" when holding the middle mouse button for 5+ seconds.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |