Wait until trigger NEW cancel timeout

[dhj49er]

I'm trying to work out wether what I see is the correct operation of this new feature or not.

When the set timeout is reached the trigger doesn't fire and the following actions are not executed. The system log shows waiting until trigger.

Is this the correct operation?

Previously I had used regular interval as a trigger and when the set time interval is reached the wait until trigger action is triggered and the macro continues with the next action.

I had expected the cancel timeout behaviour to have the same behaviour.

 

[dhj49er]

I've done further testing and established that when the cancel timeout is reached, the macro finished is triggered.

I will have to modify my macros to remove the cancel timeout and re-instate regular interval, otherwise my macros will stop working.

 

[dhj49er]

If what I've found is correct operation, I think the cancel timeout would be better if it read

Cancel macro timeout

 

[Endercraft]

If what I've found is correct operation, I think the cancel timeout would be better if it read

Cancel macro timeout

Having both options (cancel/continue macro after delay) would be great.

 

[dhj49er]

Having both options (cancel/continue macro after delay) would be great.

Agreed

 

[Dm114]

If what I've found is correct operation, I think the cancel timeout would be better if it read

Cancel macro timeout

As I suggested a long time ago, I think it would be interesting to have a boolean Magic text (like "Cancel") for all User prompt action, cancel timeout and every action with a timeout or Cancel button.

It would allow us to chose what to do when such a button is pressed: resume or cancel the macro.

 

[dhj49er]

As I suggested a long time ago, I think it would be interesting to have a boolean Magic text (like "Cancel") for all User prompt action, cancel timeout and every action with a timeout or Cancel button.

It would allow us to chose what to do when such a button is pressed: resume or cancel the macro.

Yes...having choice would be good.

However, I would have preferred the current implementation to continue the macro, not cancel it.

 

[Dm114]

Yes...having choice would be good.

However, I would have preferred the current implementation to continue the macro, not cancel it.

I understand what you mean but somebody else could prefer to cancel. It all depends on the purpose of the statement in the macro. It's the reason why I think it would be nice to be able to test a kind of "return code"

 

[dhj49er]

I understand what you mean but somebody else could prefer to cancel. It all depends on the purpose of the statement in the macro. It's the reason why I think it would be nice to be able to test a kind of "return code"

I think many users added a regular interval to wait until trigger to avoid the macro hanging in the event the trigger didn't fire.

Many users requested that a timeout is added to the wait until trigger.

Some, like me, would be expecting the new timeout to replace the functionality of the regular interval.

Hence my preference to continue not cancel.

Now, in order to know the wait timed out I have to use macro finished trigger, the same trigger that's generated when the macro runs to completion. So constraints will be required to differentiate cancelling and completing the macro and perhaps an additional macro to handle it.

This wouldn't be necessary with continue.

 

[Quidn]

Not sure but I guess that might been pushed down in priority because could (relatively simply) replaced by Regular Interval.
But yes that's not at all intuitive and actually many users couldn't find that hidden workaround unlike you.

 

[Dm114]

Not sure but I guess that might been pushed down in priority because could (relatively simply) replaced by Regular Interval.
But yes that's not at all intuitive and actually many users couldn't find that hidden workaround unlike you.

This is the magic of MacroDroid and coding...

 

[Endercraft]

Your wish has been granted !