Pretty sure this config setting only works for the built-in gSender tool change strategy - a macro would have it’s own internal configuration. May be a question for Sienci as to whether or not macros can access variables in gSender that aren’t saved in corresponding controller registers ($number things, since we’re still programming in the 80s here).
See my other thread, I’m also trying to understand how all of this stuff inter-mixes currently and it’s confusing as heck. I don’t believe there is a way to just interactively trigger a tool change (per your “go to the middle of the table and run the macro”) which is a bit confounding - I think it can only be tested/validated in the context of running a program, but I have more work to do to understand this. It’s definitely not clear or user friendly to get this stuff bootstrapped.