User Tools

Site Tools


manual:Variables

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 Both sides next revision
manual:Variables [2021/10/04 01:08]
peternlewis
manual:Variables [2021/10/04 01:08]
peternlewis
Line 42: Line 42:
 Variables with names that start or end with “Password” or “PW” are considered passwords – their values will not be stored (except in memory) and they cannot be read directly by shell scripts or AppleScripts,​ though their consequences can easily be extracted, eg with the Set Clipboard to Text action, so you should clear them as soon as they have served their purpose. ​ The Prompt For User Input dialog will display such variables concealed in a password field. Variables with names that start or end with “Password” or “PW” are considered passwords – their values will not be stored (except in memory) and they cannot be read directly by shell scripts or AppleScripts,​ though their consequences can easily be extracted, eg with the Set Clipboard to Text action, so you should clear them as soon as they have served their purpose. ​ The Prompt For User Input dialog will display such variables concealed in a password field.
  
-==== Instance Variables ​(v8+) ====+==== Instance Variables ====
  
 Variables with names that start with "​Instance"​ (case insensitive,​ trailing space not necessary) are considered private to a specific execution sequence. ​ Each time the macro is run, they will start empty but their value can be seen and changed by other macros within the same execution sequence (for example, if you execute a macro using the [[action:​Execute_a_Macro|Execute Macro]] action, that macro can see and change the instance variable (unless you execute it asynchronously which would create a new instance)). ​ Since two instances of a macro can be running at the same time, this is useful to ensure they each have their own version of the variable. Variables with names that start with "​Instance"​ (case insensitive,​ trailing space not necessary) are considered private to a specific execution sequence. ​ Each time the macro is run, they will start empty but their value can be seen and changed by other macros within the same execution sequence (for example, if you execute a macro using the [[action:​Execute_a_Macro|Execute Macro]] action, that macro can see and change the instance variable (unless you execute it asynchronously which would create a new instance)). ​ Since two instances of a macro can be running at the same time, this is useful to ensure they each have their own version of the variable.
Line 49: Line 49:
  
  
-==== Local Variables ​(v8+) ====+==== Local Variables ====
  
 Variables with names that start with "​Local"​ (case insensitive,​ trailing space not necessary) are considered local to a specific execution of a specific macro. ​ Each time the macro is run, they will start empty and no other macro will see or be able to change values. Variables with names that start with "​Local"​ (case insensitive,​ trailing space not necessary) are considered local to a specific execution of a specific macro. ​ Each time the macro is run, they will start empty and no other macro will see or be able to change values.
manual/Variables.txt · Last modified: 2023/09/29 04:44 by peternlewis