Is your feature request related to a problem? Please describe.
When trying to create a macro that inputs a longer amount of text currently requires an incredible amount of clicking:
Click the + button
Select the appropriate type (most often Tap)
Find the key on the floating keyboard, and click it
Rinse and repeat for the whole process.
Describe the solution you'd like
I'd like to greatly simplify this - I believe fairly common - procedure. Kaleidoscope already supports a macro step that types a sequence of stuff, and so should Chrysalis. Or even if not directly supporting the sequence step (which makes it a bit more complicated to simplify & compress macros for storage), we should offer a way to input a longer string, and turn it into steps.
For example, if we'd have a Custom string input step "type" when pressing the + button, which would pop up an input box we can type into (much like how the delay steps display a number input), that'd already help. Chrysalis would internally turn the string into discrete tap steps, and could even display an error state on the input if it can't. This wouldn't be perfect, because editing the string would still involve editing the generated steps one by one (in which case it might be easier to delete it all, and re-create it from scratch), but it would still be a huge improvement over the current requirement of a million clicks.
Is your feature request related to a problem? Please describe.
When trying to create a macro that inputs a longer amount of text currently requires an incredible amount of clicking:
+buttonTap)Describe the solution you'd like
I'd like to greatly simplify this - I believe fairly common - procedure. Kaleidoscope already supports a macro step that types a sequence of stuff, and so should Chrysalis. Or even if not directly supporting the sequence step (which makes it a bit more complicated to simplify & compress macros for storage), we should offer a way to input a longer string, and turn it into steps.
For example, if we'd have a
Custom string inputstep "type" when pressing the+button, which would pop up an input box we can type into (much like how the delay steps display a number input), that'd already help. Chrysalis would internally turn the string into discretetapsteps, and could even display an error state on the input if it can't. This wouldn't be perfect, because editing the string would still involve editing the generated steps one by one (in which case it might be easier to delete it all, and re-create it from scratch), but it would still be a huge improvement over the current requirement of a million clicks.