KeeperCake
Member
In the course of working with my programmer friend who doesn't like to download apps, he asked me what the distinction was between MD macros and the relatively new action blocks option. Figured the best way to answer that was with a table. Didn't really take me long.
He told me we could sum it up this way. "Macros are programs. Action blocks are functions."
Suggestions welcome for additions and edits to the table. I don't mind if someone puts the table on the Wiki. I may do it myself since I'm a prospect for access to the Wiki.
A Macro | An Action Block | |
Has a disabling switch? | Yes | No |
Can be categorized? | Yes | No |
Has a trigger component? | Yes | No |
Triggers can be constrained individually? | Yes | n.a. |
Has an action set component? | Yes | Yes |
Actions can include “Wait For Trigger?” | Yes | Yes |
Actions can be grouped into condition sets? | Yes | Yes |
Actions can be constrained individually? | Yes | Yes |
Has a constraint set component to apply to all actions? | Yes | No |
Can read & edit global variables? | Yes | Yes |
Can include local variables? | Yes | No |
Can include input variables? | No | Yes |
Can include those new “working variables?” | No | Yes |
Can include output variables? | No | Yes |
He told me we could sum it up this way. "Macros are programs. Action blocks are functions."
Suggestions welcome for additions and edits to the table. I don't mind if someone puts the table on the Wiki. I may do it myself since I'm a prospect for access to the Wiki.