All you have to do is change the behavior of the custom button to be a pad and replace the state number with x. This way when the button is pressed (x=1) a "pressed state" is performed while when the button is released a "release state" is performed.
Also, take notice, that the defined "keybout" and "keyboard_target" which you probably found from examples could be easily deleted and you can specify directly the target for the keyboard buttons by replacing the "keybout" and "keyboard_target" variables inside the scripts with your preferred kbmouse target referencing it by its index number. In the project you uploaded both are defined on target 1 (kbmouse 1) so you just have to type 1 as a target in your scripts. Read also my comments on the second set of keys!
KEYCOMBOOUT?
Re: KEYCOMBOOUT?
thanks Softcore, but doesn,t work on mac. i really don,t know where it,s the problem.
Re: KEYCOMBOOUT?
actually, this is a problem at developer level particularly for Macs and certain software (such as Cubase, even on Windows) that use Macs mapping.bite wrote:thanks Softcore, but doesn,t work on mac. i really don,t know where it,s the problem.
The only way to fix this is if a developer takes a look and SPECIFICALLY tries to create a script for the left arrow key and, possibly, the right arrow key (I gave up, don't remember if this one was troublesome too.)
The scripts do work, but there is something going on at core level that maps the Lemur arrow key script to some other key.