User Tools

Site Tools


trigger:USB_Device_Key

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Last revision Both sides next revision
trigger:USB_Device_Key [2015/07/29 10:45]
peternlewis
trigger:USB_Device_Key [2015/08/13 22:47]
peternlewis
Line 5: Line 5:
 The macro can be executed when the key is pressed, released or repeat continuously while it is held down. The trigger can also optionally be restricted to when certain modifier keys are pressed. The macro can be executed when the key is pressed, released or repeat continuously while it is held down. The trigger can also optionally be restricted to when certain modifier keys are pressed.
  
-You can configure the trigger to execute when the key is tapped (press and released quickly) each time, the first tap, double tapped, triple tapped, or quadruple ​taped (v7.0+). ​ Keep in mind that Keyboard Maestro cannot see the future, so "​tapped once" will first even if you tap the key twice ("​tapped"​ would fire both times).+You can configure the trigger to execute when the key is tapped (press and released quickly) each time, the first tap, double tapped, triple tapped, or quadruple ​tapped ​(v7.0+). ​ Keep in mind that Keyboard Maestro cannot see the future, so "​tapped once" will first even if you tap the key twice ("​tapped"​ would fire both times).
  
 For example, a macro could fire every five seconds while Control-Mouse Button 3 is held down. For example, a macro could fire every five seconds while Control-Mouse Button 3 is held down.
  
 Unlike hot key triggers, the pressed key is not removed or affected in any way. This trigger watches input devices at a low level, but it does not affect them, so any key presses continue to have their normal operation as well as triggering the macro. This is fine for modifiers, unused mouse buttons, programable keyboards and other unused buttons, but would likely be problematic for normal keystrokes which will continue to have some other, probably unwanted, affect. Unlike hot key triggers, the pressed key is not removed or affected in any way. This trigger watches input devices at a low level, but it does not affect them, so any key presses continue to have their normal operation as well as triggering the macro. This is fine for modifiers, unused mouse buttons, programable keyboards and other unused buttons, but would likely be problematic for normal keystrokes which will continue to have some other, probably unwanted, affect.
trigger/USB_Device_Key.txt ยท Last modified: 2016/01/02 03:45 by peternlewis