It would be useful if the search function could be upgraded to find a macro's "causative precedents" (other macros that contain a statement causing THIS macro to run). Many users/developers use one macro to trigger another, instead of putting a trigger condition in both macros. This feature would help answer an inevitable developer question: What makes this macro fire in the first place?
Design tool
- Thread starter hendis
- Start date