I've updated the macro to add transactions (here).
In thinking about this, both of these requests are unique to an unusual use case - i.e. starting and cancelling the macro for another purpose. While we could debate the value of the "macro canceled" message, it does inform the user that he or she has clicked the cancel button and should not expect results, which reduces support requests from novice users, and in normal use you rarely click Cancel and this is a non-issue.
We also could argue that adding CLIP to the macro does no harm, but I don't want to start complicating macros with code that is unrelated to the intended use. When maintenance is needed, I don't always remember the logic of a macro I haven't looked at in a long time, and I don't want to spend time trying to figure out the purpose of code that has no purpose when the macro is used as intended.
Since you understand the code, I suggest that you either:
1) Make the modifications in your local copy of the macro, recognizing you will have to modify any future updates too, or
2) Take the relevant portion of the code for determining the child name and place it in a separate macro for your own unique needs (you are welcome to use any of the code - i.e. it is "public domain").![smile.gif]()
| QUOTE (Yellow ants @ July 25, 2013 07:12 am) |
|
In thinking about this, both of these requests are unique to an unusual use case - i.e. starting and cancelling the macro for another purpose. While we could debate the value of the "macro canceled" message, it does inform the user that he or she has clicked the cancel button and should not expect results, which reduces support requests from novice users, and in normal use you rarely click Cancel and this is a non-issue.
We also could argue that adding CLIP to the macro does no harm, but I don't want to start complicating macros with code that is unrelated to the intended use. When maintenance is needed, I don't always remember the logic of a macro I haven't looked at in a long time, and I don't want to spend time trying to figure out the purpose of code that has no purpose when the macro is used as intended.
Since you understand the code, I suggest that you either:
1) Make the modifications in your local copy of the macro, recognizing you will have to modify any future updates too, or
2) Take the relevant portion of the code for determining the child name and place it in a separate macro for your own unique needs (you are welcome to use any of the code - i.e. it is "public domain").
