Hi PooFox,
Thanks for your response.
Yes I realize that the two CAs can be merged into another CA with a different name (and then called by a macro if need be). But this does kind of seem like a regression back to the days before subroutines and such. Each of my two CAs are very useful individually and since a CA cannot invoke another CA, I thought I might at least be able to execute them both sequentially by calling them from a macro. Thus saving a lot of inline expansion of the same code in two places. The CAs are about 18 lines long each. It's not a big deal since I can replicate them by exporting and then importing them but, I'm just trying to find the most efficient way of doing things while trying to learn the 'can and can't do rules' as I go
BTW you
can call a single CA from a macro just like any other action at least as long as there are no other CAs in the list of actions collected into the macro.
Rejoice,
Bob