Move to current action from log

[DonDemon]

Sometimes, it's really hard what action is changing variable and where. As right now I'm working on one my huge macro with a large number of variables and "while" actions that is making macros really longer in log, it's impossible to understand what action is changing variable right now (and where is this action)

 

[Dm114]

Sometimes, it's really hard what action is changing variable and where. As right now I'm working on one my huge macro with a large number of variables and "while" actions that is making macros really longer in log, it's impossible to understand what action is changing variable right now (and where is this action)

To help you debugging your macros, you can use this Action block:

Help in debugging macros and Action Blocks

When debugging a macro, it's sometimes useful to know the value of some variables during the process. In a macro, it's possible to stop execution and check values of the suspect variables. In an Action Block it's much more complicated. Moreover, when execution stops (Cancel action) it's not...

www.macrodroidforum.com

 

[DonDemon]

To help you debugging your macros, you can use this Action block:

Help in debugging macros and Action Blocks

When debugging a macro, it's sometimes useful to know the value of some variables during the process. In a macro, it's possible to stop execution and check values of the suspect variables. In an Action Block it's much more complicated. Moreover, when execution stops (Cancel action) it's not...

www.macrodroidforum.com

Thanks, but I think it will not help me because I'm trying to find the reason why is the macrodroid crashing (it's abviosly because of one of "while" conditions that become infinity). So the problem is that there are around 20 variables, 2 main macros and 2 core macros, so it is will be impossible to track wrong if/while only by variables

 

[Dm114]

Thanks, but I think it will not help me because I'm trying to find the reason why is the macrodroid crashing (it's abviosly because of one of "while" conditions that become infinity). So the problem is that there are around 20 variables, 2 main macros and 2 core macros, so it is will be impossible to track wrong if/while only by variables

I understand what you mean. I guess the Do/While loop doesn't directly involve 20 variables, so you could first check these variables just before Loop statement. It could give you some ideas on the origin of the infinite loop.

Then try to follow the/these variable(s) inside the loop...

But, of course, it's not easy with a great number of variables in a big macro!

 

[Endercraft]

I wish there was an action to log to system log, right now I'm debugging a program (also because of a crash) and throwing in a bunch of logs is really easy and helps a lot to pinpoint where exactly it happens.

 

[DonDemon]

I wish there was an action to log to system log, right now I'm debugging a program (also because of a crash) and throwing in a bunch of logs is really easy and helps a lot to pinpoint where exactly it happens.

+,but initial in title I mean to add ability to move to current action by holding it. Or just to add id for every actions including if and while