User Input in KM

[kevinjhardman]

Pardon the naive Keyboard Maestro question.

I want to create a macro to prompt me to input a name into a dialog box that I will then paste in to an OmniFocus task.

I see KM action: Prompt for User Input but am not clear how I use this action to capture an input. Once the macro has the stored value, what action do I use to paste the value?

I am comfortable with the OmniFocus side of the macro.

Thanks in advance.

[vincent_ardern]

As per the below image, the prompt for user input action sets the user input to the appropriate variable (first column). You can then use that variable as I have in the second action.

I have used an instance variable (but you should use a local variable, see below for why). I've also used the double underscore technique to just show "details" in the prompt box.

[JMichaelTX]

@vincent_ardern

I have used an instance variable

As I have recently learned, it would be best to use a Local variable in this case, rather than an Instance variable.
Instance variables are really only advised when you plan to share the variable with a Sub-Macro.

For more info, see

The Important Distinction Between Local and Instance Variables

Reference: Variables in the KM Wiki Yes, there is good reason to use both Local and Instance Variables. Consider this simple loop: Set variable “Instance Count” to 3 Set variable “Instance Index” to 1 While calculation Instance Index <= Instance Count Do stuff in an Execute a Macro action (aka Sub-Macro) Set variable “Instance Index” to “Instance Index + 1” If that Sub-Macro changes the value of Instance Index or Instance Count, then the main macro will not behave as expected. Now th…

[vincent_ardern]

I couldn't decide upon that myself. I hedged my bets that the OP would potentially have submacros and didn't want my example to mess him up if he did, but in hindsight I should probably have gone with local and then let him ask follow up questions. Edit original post. Thanks

[kevinjhardman]

Thank you both. Is my nomenclature correct here?

[Tom]

Seems fine. But, as mentioned by @vincent_ardern, I would use two underscores in the variable name, to prevent the ugly “Local” prefix from appearing in the prompt window: Local__Details

[kevinjhardman]

Thank you for your help!