Hi Rob, love your software and it's a daily staple for me, thanks so much for you hard work.
I have 2 separate questions:
First:As you can see, the drop down menu where I select/define the Virtual Key is reset to its "empty" position; this appears to happen to ALL of my steps with virtual keys (so, dozens)
whenever Strokesplus options are opened. However, they still seem to be working correctly.
Is this just a UI glitch, or is there a problem with VKs? Should I edit all of my gestures containing VK steps to fire traditional hotkeys where possible? As you know, most keyboards don't have hotkey access to most of these virtual functions (like "BROWSER_BACK" or "MEDIA_NEXT_TRACK), so I'm hoping not.
Second question:What exactly is the relationship between the "Steps" and "Script" tabs for each gesture? I always assumed that, for example, if I had a step that fired the virtual key "BROWSER_BACK", then I'd need a corresponding "sp.SendVKey(vk.BROWSER_BACK);" in the script tab. After all, that's how your default example is set up.
However, it appears that many of my custom steps that call for hotkeys/virtual keys have empty script areas, yet they still work. Conversely, if I were to add the script but remove the step, it doesn't work. If I were to add the script for a completely different key, only the "steps" defined key will fire.
So, are scripts for hotkeys/virtual keys simply not necessary? Do steps simply take precedence over scripts? I use a global mouse-wheel script that doesn't even have steps! Does that mean steps and scripts are independent of each other entirely? Or is it just that keyboard events and mouse events are separate? You can see my confusion here
I'm fully aware that these are minor "issues"; I'm just seeking some clarification. I've spent a lot of time creating a ton of gestures so I'm just worried if I'm doing something wrong; plus, some clarity will help me continue learning how to create more interesting actions.
Thanks again for this great software, and any help would be greatly appreciated.