V5.37 - Feedback

[MacroDroidDev]

For obvious bugs, please use report a bug in troubleshooting section with a clear description.

For other issue and discussions (related only to this beta), please leave all feedback here.

 

[sampleuserhere]

{fg_app_name} doesn't get refreshed when any of non application window exits focus.

This is legacy behaviour, idk since when.

https://imgur.com/EzaO2Mh

 

[Quidn]

I'm so excited to use several awaited features!
It seems that there were significant changes even in not so visible.

Local Variables section persists its height when shown in inline view​

• It scrolls if a variable is added. Problem gone if save and open again, but happens again if add a new one.

New "Macro Finished" trigger doesn't fire when macro canceled​

• It seems that the trigger does fire by something similar to "the last action", so won't be fired when the macro is canceled(e.g., timed out by actions including Wait Until Trigger and Confirm Next).
• It does make sense since canceled might not be regarded as finished, but I think it should be fired too whatever the reason to stop the macro.
• It'd better if it could be fired even after crashes, but that might too much wish.
• However I love this new trigger even in current state!

 

[MacroDroidDev]

Thanks @Quidn

That is exactly the sort of issue I was expecting to see with the large edit macro screen changes. I'm going to look at this now and get a new beta out later today.

The macro finished trigger should fire however the macro ends (but after crashes is not going to be possible), so I will also try and correct this for the next update.

 

[MacroDroidDev]

@sampleuserhere Can you please clarify exactly what the issue with {fg_app_name} is?

 

[sampleuserhere]

@sampleuserhere Can you please clarify exactly what the issue with {fg_app_name} is?

My bad, I didn't leave any details about the screen record I attached here.

{fg_app_name} doesn't get refreshed when any of non application window exits focus.

This is legacy behaviour, idk since when.

https://imgur.com/EzaO2Mh

The floating text on the top right shows {fg_app_name} as the content. I started the floating text individually by running the action directly with "test action".

As you can see at the beginning, It displayed Vivaldi, which is the browser that was opening two tabs. Then when I opened up the keyboard it displayed Gboard.

The odd behaviour started when Gboard was not "foreground" any more, out of focus. The floating kept displaying "Gboard", while I think it should be "Vivaldi".

The same behaviour occured when I interacted with Everywhere Launcher (side gesture app), It didn't revert back to Vivaldi either even when I already interacted with Vivaldi afterwards.

Is this explanation sufficient?

 

[MacroDroidDev]

@sampleuserhere thanks for clarifying, I must confess I didn't even notice you had posted a video (I though it was just an image). I've been playing around with the accessibilty service that drives this feature and it doesn't look good. The events that I get when I close the keyboard suggest the android system ui is the foreground app and that is all I get.

I'm going to investigate if the Usage Access stuff is more reliable for this feature (but that has it's own quirks).

 

[henne10]

Added com.wireguard.android.permission.CONTROL_TUNNELS permission to Manifest.

Thank you for this!

 

[sampleuserhere]

@sampleuserhere thanks for clarifying, I must confess I didn't even notice you had posted a video (I though it was just an image). I've been playing around with the accessibilty service that drives this feature and it doesn't look good. The events that I get when I close the keyboard suggest the android system ui is the foreground app and that is all I get.

I'm going to investigate if the Usage Access stuff is more reliable for this feature (but that has it's own quirks).

Now that I have a look at it, it really does look like an image lmao

Anyway, I wonder if it's a good approach to run something like read screen action everytime those close event occurs?

TouchTask plugin Read Screen action outputs the window type.



And there is this one last array child that returns "application", and it's always the current foreground application window. I'm not sure though which API the dev is using.

 

[MacroDroidDev]

Thanks @sampleuserhere I will take into this when I can.

 

[Quidn]

Fixed issue where edit macro screen would not scroll properly when macro description is shown.

I was one step late. Even a screen recording was ready to be embedded.

Fixed well in V5.37.3. You are always so fast!

 

[Dimlos]

I found a minor display problem and would like to report it.
When the font size is reduced, the If text is cut off and the action column in the action block is not reduced in size.
I would appreciate it if you could fix this problem, although it is not a priority because it does not affect the macro operation.

 

[Endercraft]

I found a minor display problem and would like to report it.
When the font size is reduced, the If text is cut off and the action column in the action block is not reduced in size.
I would appreciate it if you could fix this problem, although it is not a priority because it does not affect the macro operation.

Any bug you find (even if it's the smallest bug ever) you should report via the report bug button in the troubleshooting section.
That's what I've been doing this entire time

 

[Quidn]

There are two bugs are shown in the screen recording above.

1. Checked items outside the visible area are ignored.
2. Actually I thought the text being cut off was a sort of side effect rather than a bug. I'll show exact symptom of this either.

Any bug you find (even if it's the smallest bug ever) you should report via the report bug button in the troubleshooting section.
That's what I've been doing this entire time

That's absolutely true that in-app reporting is strongly recommended at most.
But for this kind of bugs, screen recording might more intuitive than in-app report, I guess.

 

[Endercraft]

Have you reported through the bug report system too ? If not please do so.

 

[CDA]

Hello, having a problem with constraints, at the moment only noticed it when using "Bluetooth device connected" it always returns as false and prevents the action, even when the device is definitely connected. Must be an issue in the new version as these macros were working fine before the update and have not been changed since.

NOTE: I did submit a bug report in the app.

 

[Endercraft]

Hello, having a problem with constraints, at the moment only noticed it when using "Bluetooth device connected" it always returns as false and prevents the action, even when the device is definitely connected. Must be an issue in the new version as these macros were working fine before the update and have not been changed since.

NOTE: I did submit a bug report in the app.

This is a known issue that for some reason seems hard to fix. @MacroDroidDev may know why it's so 'hard' to fix.

 

[CDA]

This is a known issue that for some reason seems hard to fix. @MacroDroidDev may know why it's so 'hard' to fix.

Ah ok, a quick search didn't show any threads but I may not have been looking for the right terms. Is it a recent issue? The constraints were working fine for me until the update.