Merge Action Blocks and Macros - Parameters for Macros or local variables for Action Blocks

[cwallen19803]

I'm sure there is a good reason or limitation that dictated the way Action Blocks differ from Macros. I think the Action Blocks are a great addition, but to be honest I think that adding parameters to Macros would have been better than removing local variables from Action Blocks.

I'm going to guess that Action Block parameters are simply local variables treated differently. Is there any way you can add an attribute to Macro local variables so that it looks like a parameter to me? That way we'd have the best of both in one unit.

 

[tanutanu]

I'm sure there is a good reason or limitation that dictated the way Action Blocks differ from Macros. I think the Action Blocks are a great addition, but to be honest I think that adding parameters to Macros would have been better than removing local variables from Action Blocks.

I'm going to guess that Action Block parameters are simply local variables treated differently. Is there any way you can add an attribute to Macro local variables so that it looks like a parameter to me? That way we'd have the best of both in one unit.

Currently, output parameters are working as the "local variable" alternatives.
I requested the local variables for the Action blocks like this;

"iocal variable"
I don't mean just same as the local variable of standard macros. It works as same as the current output parameter internally, but has only one limitation NOT to return the value to avoid unexpected mistakes. It shows in another field like normal local value of regular macros, but never keep the value, only for the current instance. It makes a dialog small and short on an action statement in a caller macro as well.