Hello all.
Compared to other computer languages and scripting, Macrodroid, as far as I can tell, possesses a peculiar perk inasmuch as it is possible, and it often happens (at least in my macros), that the same macro can be re-invoked while a previous invocation of it has not yet completed and is therefore still running. This can occur repeatedly and in some cases multiple invocations may be all executing simultaneously. In these situations, it is important to antecipate all possible interactions of the macro in question with itself, a problem which is compounded by the fact that all concurrent invocations will be using the same set of local variables.
Although this MD characteristic may sometimes cause some head scratching and needs to be addressed with caution, personally I find it quite useful and elegant, as it makes it possible to place several related functions in the same macro, each called by its own trigger or invocation method and thus identified and separately processed.
What are your impressions and experiences regarding this matter? How do you usually handle it? Do you think this system works well as it is or it should be altered in any way?
Compared to other computer languages and scripting, Macrodroid, as far as I can tell, possesses a peculiar perk inasmuch as it is possible, and it often happens (at least in my macros), that the same macro can be re-invoked while a previous invocation of it has not yet completed and is therefore still running. This can occur repeatedly and in some cases multiple invocations may be all executing simultaneously. In these situations, it is important to antecipate all possible interactions of the macro in question with itself, a problem which is compounded by the fact that all concurrent invocations will be using the same set of local variables.
Although this MD characteristic may sometimes cause some head scratching and needs to be addressed with caution, personally I find it quite useful and elegant, as it makes it possible to place several related functions in the same macro, each called by its own trigger or invocation method and thus identified and separately processed.
What are your impressions and experiences regarding this matter? How do you usually handle it? Do you think this system works well as it is or it should be altered in any way?
Last edited: