Hello!
It is now that if a trigger has launched the Macro while it is already running (by the other trigger, for example), then there will be launched a new copy of the same macro. If the previous copy is still running in a cycle, then there will be 2 copies in memory, running simultaneously and in conflict. And it may be a problem!
Now I have to make some other 'starting' macro, that firstly terminates/stopes the running macro and relaunches it again, since the macro cannot terminate self-copies and continue running. It is very unpleasant.
I suggest to make a command to terminate any running previous copies of the macro and continue working So we could use this command at the very beginning of the macro to ensure that no other copy of the same macro is running at the same time. I think it could be done as an option of 'stay running' for the present command of stopping the macro. Now it terminates all the copies, including that has it invoked.
Thanks.
It is now that if a trigger has launched the Macro while it is already running (by the other trigger, for example), then there will be launched a new copy of the same macro. If the previous copy is still running in a cycle, then there will be 2 copies in memory, running simultaneously and in conflict. And it may be a problem!
Now I have to make some other 'starting' macro, that firstly terminates/stopes the running macro and relaunches it again, since the macro cannot terminate self-copies and continue running. It is very unpleasant.
I suggest to make a command to terminate any running previous copies of the macro and continue working So we could use this command at the very beginning of the macro to ensure that no other copy of the same macro is running at the same time. I think it could be done as an option of 'stay running' for the present command of stopping the macro. Now it terminates all the copies, including that has it invoked.
Thanks.