User Tools

Site Tools


action:Prompt_for_User_Input

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
action:Prompt_for_User_Input [2017/09/26 01:16]
peternlewis
action:Prompt_for_User_Input [2019/06/30 22:04] (current)
peternlewis
Line 1: Line 1:
-{{:​action:​form-icon.png?​nolink |}} 
 ====== Prompt For User Input ====== ====== Prompt For User Input ======
  
 _Prompt For User Input_ allows you to design a form that will ask for user input, storing the results in [[manual:​Variables|Keyboard Maestro Variables]]. _Prompt For User Input_ allows you to design a form that will ask for user input, storing the results in [[manual:​Variables|Keyboard Maestro Variables]].
 +
 +You can prompt for variables with text, checkbox, popup menu, or password fields.
 +
 +{{ promptaction.png?​nolink&​575x402 | Prompt Action }}
  
 ===== Example ===== ===== Example =====
  
-**This Setup of the Prompt for User Action . . .**+This action:
  
-{{:​action:​promptaction.png|}}+{{ promptfullaction.png?​nolink&​575x612 ​Prompt Example Action ​}}
  
-**Produces this Display***+Produces this Display:
  
-{{:action:promptwindow.png|}}+{{ promptwindow.png?​nolink&​585x505 ​Prompt For User Input Window ​}}
  
 ===== Form Fields ===== ===== Form Fields =====
Line 134: Line 137:
  
 The [[token:​PromptButton|%PromptButton%]] token (v8+) is set to the _name_ of the button pressed, and can be used in actions later in this instance like any other text token. ​ The deprecated _Result Button_ variable is also set to the _name_ of the button pressed. The [[token:​PromptButton|%PromptButton%]] token (v8+) is set to the _name_ of the button pressed, and can be used in actions later in this instance like any other text token. ​ The deprecated _Result Button_ variable is also set to the _name_ of the button pressed.
- 
-Note that the system will not allow Keyboard Maestro Engine to see keys typed in its own windows so the [[trigger:​Typed String | Typed String triggers]] will not work within Keyboard Maestro Engine windows. 
  
 === How Buttons are Processed === === How Buttons are Processed ===
Line 159: Line 160:
  
 An update is planned so that if the first button has the Cancel Macro flag, then it is not the default (by default), and if the second button does not have the Cancel Macro flag, then it does not get the Escape/​Command-,​ key (by default). An update is planned so that if the first button has the Cancel Macro flag, then it is not the default (by default), and if the second button does not have the Cancel Macro flag, then it does not get the Escape/​Command-,​ key (by default).
 +
 +===== Notes =====
 +
 +Note that the system will not allow Keyboard Maestro Engine to see keys typed in its own windows so the [[trigger:​Typed String]] triggers will not work within Keyboard Maestro Engine windows.
  
 Note that the system really really wants a "​default"​ button, and if you do not give it one, it will choose one for you. Note that the system really really wants a "​default"​ button, and if you do not give it one, it will choose one for you.
action/Prompt_for_User_Input.1506403019.txt.gz ยท Last modified: 2017/09/26 01:16 by peternlewis