opening the keyboard and mouse icon picture and pressing Record button there and assigned it directly to square button). I guess you have recorded the macro and assigned it to Square button via the Controls tab page of profile editor (ie. Also, flushing the hid queue several times a second just creates unnecessary overhead.
events in a queue which haven't been processed yet are flushed to hyper space). I recommend you to untick this because by flushing the HID message queue each time an event is read from a hid device may loose some events (ie. Tested it again using the square btn as macro trigger key and the macro repeated square button presses. Anyway, my test macro using Cross trigger simulated number of cross btn presses. The next release should have that touchpad fix.Īah. There was a small bug there but it is already fixed in the latest development version. It is easy to forget to press the save button on the bottom of the spec action screen and just pressing the top toolbar save btn.Īfter you have saved a special action (macro, load Profile, whatever) then you have to enable the spec action in a profile by selecting the checkbox in a list of spec actions and then save a profile.Īnother issue you mentioned was about using a touchpad for mouse controlling. When you edit a macro then did you remember to press "Save" button on the bottom of the macro special action screen? You have to press this macro specific "Save" button before you press the "Save" on top toolbar to save the whole profile. I set the macro to execute via Options btn.Įnabled this macro in a profile and Options btn repeated the X btn events with defined wait intervals just fine. I just tested to record a macro with "auto fire" type of sequence (X btn down, short wait, X btn up, short wait and repeating the same few times).
0 kommentar(er)
