Wait action: duration with decimal value

[Dm114]

I sometimes use Wait action to make my torch blink

When using Wait action with a fixed duration, we can select it in minutes, seconds and milliseconds and waiting time seems to be accurate.

When selecting a variable, we only can select the unit (minutes or seconds) and duration seems to be truncated to whole numbers when using a decimal value. I.e. 0 to 0.9 seconds is interpreted as 0 second, 1 to 1.9 as 1 second, and so on. So it's impossible to make torch blink on a variable pace unless with a whole number of seconds.

Would it be possible either to select milliseconds in addition to the current 2 units (if duration must be a whole number) or use decimal values?

 

[Abalsam]

I sometimes use Wait action to make my torch blink

When using Wait action with a fixed duration, we can select it in minutes, seconds and milliseconds and waiting time seems to be accurate.

When selecting a variable, we only can select the unit (minutes or seconds) and duration seems to be truncated to whole numbers when using a decimal value. I.e. 0 to 0.9 seconds is interpreted as 0 second, 1 to 1.9 as 1 second, and so on. So it's impossible to make torch blink on a variable pace unless with a whole number of seconds.

Would it be possible either to select milliseconds in addition to the current 2 units (if duration must be a whole number) or use decimal values?

While building in this functionality would be ideal, I can envision a way to do this using loops. However, while I was trying to build a test macro to illustrate this, I found that the repeat action (variable # of times) loop is no longer working in MD version 5.23.

Here is the link to the POC macro I uploaded. I implemented the loops using two different methods as the first method did not work in 5.23 http://www.macrodroid.com/macrostore?id=12279.

 

[Dm114]

While building in this functionality would be ideal, I can envision a way to do this using loops. However, while I was trying to build a test macro to illustrate this, I found that the repeat action (variable # of times) loop is no longer working in MD version 5.23.

Here is the link to the POC macro I uploaded. I implemented the loops using two different methods as the first method did not work in 5.23 http://www.macrodroid.com/macrostore?id=12279.

It can be interesting for test purpose but I think that @MacroDroidDev will improve the behavior of the Wait action. Let's wait'n see!

 

[Dm114]

Hi Jamie.
Do you think you could improve Wait action a bit?

 

[FrameXX]

This is actually a bug that came in with last update. Hopefully it will be fixed. I already troubleshooted this bug too.

 

[FrameXX]

While building in this functionality would be ideal, I can envision a way to do this using loops. However, while I was trying to build a test macro to illustrate this, I found that the repeat action (variable # of times) loop is no longer working in MD version 5.23.

Here is the link to the POC macro I uploaded. I implemented the loops using two different methods as the first method did not work in 5.23 http://www.macrodroid.com/macrostore?id=12279.

Waiting n times for 1 milisecond is also a solution, but I found it to be power consuming and not much accurate.

 

[Dm114]

This is actually a bug that came in with last update. Hopefully it will be fixed. I already troubleshooted this bug too.

Thank you for confirming it's a new bug because I was wondering why torch blinking on incoming calls became erratic!

Waiting n times for 1 milisecond is also a solution, but I found it to be power consuming and not much accurate.

You're right, this solution is not really satisfying. Mainly if this bug has to be fixed.

 

[Dm114]

This is actually a bug that came in with last update. Hopefully it will be fixed. I already troubleshooted this bug too.

I just downloaded 5.23.9 version but it's not fixed yet...

 

[newdad]

Hi. I just purchased the full version of MacroDroid and was looking to set up a small random delay value using a variable for a project and found the options to only be seconds and minutes. With some quick googling, stumbled onto this thread about milliseconds being an option only as a specific defined constant value. Just looked and sure enough it's like that. Has there been any update to this? Thank you.

 

[Endercraft]

Hi. I just purchased the full version of MacroDroid and was looking to set up a small random delay value using a variable for a project and found the options to only be seconds and minutes. With some quick googling, stumbled onto this thread about milliseconds being an option only as a specific defined constant value. Just looked and sure enough it's like that. Has there been any update to this? Thank you.

You can do this if you set an integer variable, select it in the wait action, delete that variable, create a decimal variable with the same name then changing that variable.

 

[newdad]

You can do this if you set an integer variable, select it in the wait action, delete that variable, create a decimal variable with the same name then changing that variable.

Sounds creative. I think I'm missing something because I keep ending up with a Wait action that I can't get around with the same problem of not being able to set a millisecond option if it's a filled by a variable. I have to randomize the value by using a variable.

Does the developer still upkeep the app? Maybe this is still on the bug list and an update on timer could be provided. Thanks.

 

[Dm114]

Sounds creative. I think I'm missing something because I keep ending up with a Wait action that I can't get around with the same problem of not being able to set a millisecond option if it's a filled by a variable. I have to randomize the value by using a variable.

Does the developer still upkeep the app? Maybe this is still on the bug list and an update on timer could be provided. Thanks.

Do you really need such a tiny duration (in milliseconds)? I'm not sure of a reliable accuracy below some tens of milliseconds anyway...
But you theoretically can reach it with @Endercraft's workaround

 

[Endercraft]

Does the developer still upkeep the app? Maybe this is still on the bug list and an update on timer could be provided.

Then developer is still actively maintaining the app,in fact he should come respond to some threads here before Tuesday.
Sometimes features are requested and don't get added even for 2 years but this is due to the limited development time, but this should hopefully change soon.

 

[newdad]

Randomized delays--especially sequential ones in the same event window--create more of the appearance of a human touch on response instead of a repeated and consistent one-second or zero-second delay when tapping buttons. I'm thinking random millisecond values between 200 and 1400 sandwiched in between each press would fit pretty nice. I can afford the time, but just need the effect.

I am brand new to MacroDroid, so I honestly haven't spent the time yet to figure out the basics and tweaks of it yet. I'll keep cracking at it to see if I can figure out the workaround since you guys took the time to help me out with the option. Thanks.