![]() For example if I want to move the cursor to a certain location as long as a key on a USB controller is pressed down and want to store the initial mouse position in order to get back there after release the auto-repeated key trigger causes the store action to immediately pick up the new location with the first auto-trigger - making this step useless.sure I can find a workaround for this with setting a variable flag definition and a if/then loop definition, but that's really bulky.Īnd one big issue: I'm using Parallels Desktop and want to use macros there too. ![]() I also have the problem that I need to keep KM from interpreting the automatic trigger repeats once a key is down for longer. Just some other questions (sorry, absolute beginner here) - is there any simple and compact way of programming one macro for "do x once a key is pressed and holded (maybe a pretty long time, like a modifier key while tab-stepping through applications) and then do y once the key is released" ? Or do I always need to setup two macros separately, one for "key is down" and one for "key is released" ? The problem is, that when I use the "Execute Actions Until Conditions Met" action there's no way of choosing the USB device key (X-Keys USB module) I want to use as condition target - compared to the initial trigger selection menu (FEATURE REQUEST!).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |