Thanks for the reply, @peternlewis.
Yes, and in most cases it works very well. Thank you for that!
My OP is addressing the cases when submacros or subroutines:
-
are general in nature, i.e., could be called by a variety of macros unrelated to one another (thus the callers are in unrelated macro groups),
-
might be refined over time, and
-
will be shared on the forum (thus imported).
The example I provided, sm.𝗽𝗮𝗹𝗲𝘁𝘁𝗲⇾MoveMouseToPalette, is such a macro. As I'm sure you recognize, submacros or subroutines like this can be incredibly useful because functionality can be created once and used many places.
I suspect you are referring to my above suggestion. If that's the case, I'm not surprised, and frankly that's why I created a method to provide some protection.
My main objective with the OP was to raise awareness and to provide a thread for discussion. Hopefully it has helped you understand an issue that some users encounter. (I've seen many examples of this on the forum and the solution you ultimately roll out exceeds expectations.)