v5.49 - Feedback

[GamBIT]

the present array sorting action works as
A, B, С, D, E, .... a, b, с, d, e, ...
We search for the value in upper case and cannot find it if a value starts with a low case symbol.
Dear author, can You change it at the next beta to the more friendly listing like A, a, B, b, С, с, D, d, E, e ... ?
The same is for the local languages sorting further in the listing - it is better if the listing wasn't case-sensitive.
I often flow such the arrays to the selection dialogs, and now it is not easy to find a value in the case-sensivite listing.
Thanks.

 

[MacroDroidDev]

the present array sorting action works as
A, B, С, D, E, .... a, b, с, d, e, ...
We search for the value in upper case and cannot find it if a value starts with a low case symbol.
Dear author, can You change it at the next beta to the more friendly listing like A, a, B, b, С, с, D, d, E, e ... ?
The same is for the local languages sorting further in the listing - it is better if the listing wasn't case-sensitive.
I often flow such the arrays to the selection dialogs, and now it is not easy to find a value in the case-sensivite listing.
Thanks.

It definitely should not be like that, I shall investigate and resolve.

 

[MacroDroidDev]

the next bug I have mentioned earlier..

If we copy a trigger from one macro to another, and next edit its properties, MD can still refer to the old ones, showing the new properties.

The next macro shows 2 correct triggers and 2 incorrect.
The correct triggers are made inside the macro, Application Launched, with pointing the dictionary as a source for the applications. It works as expected.
The incorrect ones are copied from another macro with the other dictionary variable, next were edited. And it still continues to refer to that old variable 'Apps_selected_for_force_rotate', despite it has been changed to the 'Apps_selected_for_force_screen_on'. So the incorrect triggers fire when launching the app from the 'Apps_selected_for_force_rotate' dictionary while at the triggers is shown the 'Apps_selected_for_force_screen_on' dictionary. I have spent a lot of time trying to understand what is going on.

By the way, exporting this macro I have noticed that all the variables were not exported. Previously I thought that MD is exporting all related to the macro. No? Or it may be a part of the problem?

p.s.
It seems to me I haven't bumped into this problem some versions ago. Maybe it has appeared in some recent version.

The attached macro does not contain any references to Apps_selected_for_force_rotate so it's not possible to tell you much from this I'm afraid. Once again I have tried to copy triggers between macros and update them and I'm not seeing any kind of problem.

If you are able to recreate the problem reliably please share exact steps I can follow to reproduce the issue.

 

[GamBIT]

The attached macro does not contain any references to Apps_selected_for_force_rotate so it's not possible to tell you much from this I'm afraid. Once again I have tried to copy triggers between macros and update them and I'm not seeing any kind of problem.

If you are able to recreate the problem reliably please share exact steps I can follow to reproduce the issue.

I have that macro working with the variables (dictionaries). Maybe this is a reason.. Sharing this macro that variables are not being exported. But this phantoms act reliably in my configuration. So that I did it in intent to recreate, and it worked. Somehow MD continues to link to the old variable at that triggers. And even if I was changing it again the incorrect triggers remained to refer to the old dictionary. But this happens ONLY if I copy/paste the triggers. If you just create it, the issue doesn't happen. That' all I have to say now.
By the way, if the global variables in the triggers are not now to be exported with a macro, I guess its worth doing as the macro would not run in a proper way.
Thanks.

 

[GamBIT]

It definitely should not be like that, I shall investigate and resolve.

Moreover, the case-sentitive string array sorting is now that does like ACR, AIDA64, AccuBattery...
Notice that the correct non-case-sensitive sorting must be in order like AccuBattery, ACR, AIDA64...

 

[pluto25]

SOLVED with 5.49.11 - thx!

5.49.10 Not all array entries shown in <display dialog>

Please see in the attached macro, only the very first and the very last entries (out of a total of 18 entries) are shown in the display dialog command.

 

[md_sgf]

I have that macro working with the variables (dictionaries). Maybe this is a reason.. Sharing this macro that variables are not being exported. But this phantoms act reliably in my configuration. So that I did it in intent to recreate, and it worked. Somehow MD continues to link to the old variable at that triggers. And even if I was changing it again the incorrect triggers remained to refer to the old dictionary. But this happens ONLY if I copy/paste the triggers. If you just create it, the issue doesn't happen. That' all I have to say now.
By the way, if the global variables in the triggers are not now to be exported with a macro, I guess its worth doing as the macro would not run in a proper way.
Thanks.

Works fine for me (tested on v5.49.9)

What if you recreate the 2 macros that you are copying triggers between - maybe they are a bit corrupted?

 

[GamBIT]

Works fine for me (tested on v5.49.9)

What if you recreate the 2 macros that you are copying triggers between - maybe they are a bit corrupted?

The macro those 2 were copied from, works properly. Since it refers to the proper dictionary.
I'll try to recreate it with mdr if the author would not be able to find the reason basing on the given info and macro.

 

[MacroDroidDev]

5.49.10 Not all array entries shown in <display dialog>

Please see in the attached macro, only the very first and the very last entries (out of a total of 18 entries) are shown in the display dialog command.

I believe all items are there but the ordering is broken and does not match the ordering when (for example) showing in the edit screen. It appears that the sorting is not done when the text is output via this mechanism so I will correct this shortly.

 

[pluto25]

Yes, you are right! It is obviously only a matter of correct sorting.

 

[pluto25]

I believe all items are there but the ordering is broken and does not match the ordering when (for example) showing in the edit screen. It appears that the sorting is not done when the text is output via this mechanism so I will correct this shortly.

Thx! Solved with 5.49.11

 

[pluto25]

Edit: deleted here since reported from the MD app "Report a bug" feature.


5.49.11 selection of variables is corrupted in <text manipulation>

see enclosed video (and try it yourself) with the attached macro: when trying to add a <text manipulation> action, the first three steps
1) selection of the source variable
2) selection of the text to match
3) selection of the target variable
are skipped. Instead, MD has directly chosen an array variable and asks for the index to be used.

You have to rename the .mp4.txt file to .mp4

 

[pluto25]

Edit: deleted here since reported from the MD app "Report a bug" feature.


5.49.11 losing start and stop indices in <subarray> array manipulation

What I already mentioned here but what I can't that time reproduce is now easily reproducible:

If you have <subarray> array manipulations which have fixed values for start and stop indices (in my case 0 and 1000) these values get lost in all subarray array manipulations if you change the name of an array variable. Check it with the attached macro or see the video.

Interestingly, also subarray array manipulation actions are affected which are not using the renamed array as source or as target! Secondly, the only way to prevent the observed deletion of the start and stop indices is the use of variables instead of fixed values (as shown in the 4th subarray array manipulation).

You have to rename the .mp4.txt file to .mp4

 

[huashimacro]

The floating button is no longer displaying. In versions of MacroDroid after 5.49.5, the floating button often does not show, whereas it could display normally in previous versions. Even when the macro is turned on, the floating button does not appear. System: Xiaomi Android 15.

 

[md_sgf]

What if you recreate the 2 macros that you are copying triggers between - maybe they are a bit corrupted?

What i meant was maybe the original triggers (in the original macro) are partially corrupted. So, see if recreating the original triggers in the original macro, and then try to copy them again, eliminates this issue.

 

[GamBIT]

What i meant was maybe the original triggers (in the original macro) are partially corrupted. So, see if recreating the original triggers in the original macro, and then try to copy them again, eliminates this issue.

I tried to recreate the issue with the triggers but nothing happened. Maybe this is caused the wrong saving the mdr and restore. I dont know. The only way is to do a lot of work deleting all other things in the project to leave only the macro and the 2 vars.

 

[GamBIT]

I wanna ask the Developer - is it a common situation if the Sensor Light Trigger doesn't fire every time it must? It fires sporadically. Maybe 7/10. Sometimes it stops firing at all for some time. Even if I switch the light in the room on/off to the whole darkness. Although I see that MD is seeing the lux value correctly if I open the tuning window for this trigger while it is running. How nice it could be if this trigger could fire every time it has. Reliably.. Now I have to duplicate this function with the Regular Interval trigger, but it isn't nice.
The other problem is that if a sensor light trigger is fired and in the macro is a check of the same Sensor Light 'if condition', then to my wonder I see that the trigger is fired but the macro doesn't see this light condition. For example, the trigger is 'less then 5.0 lux' is fired, but 'if condition' returns false for the same 'less then 5.0 lux' condition. The 'if' action is running at the very beginning of the macro, it has no time lag between the trigger and the 'if' action. How can it happen?
By the way, it was the reason why I have decided, if possible, to stop using an if-condition 'the trigger is fired', if there is a paired to this trigger if-condition for the same function. I just run the macro and it checks for this condition instead of trigger. Just because I cannot be sure that the trigger will fire reliably in all the cases.

 

[md_sgf]

Did you try to point only the macro's name manually? It seems that way MD would search for the macro not by id but typed name.. ? So id wont brake.

Actually, this method can only be done with macros, i now realize...

 

[GamBIT]

Actually, this method can only be done with macros, i now realize...

But if you decide to change the macro's name later... it would be a nightmare searching in all the macros for all the reffering links.
What's why I suggested to make changes to MD so that if a link contains both id and name, and the id has been deleted and restored with the other id but the same name, then MD would use its name to run, and maybe just change the id for the macro of the same name.

 

[md_sgf]

I wanna ask the Developer - is it a common situation if the Sensor Light Trigger doesn't fire every time it must? It fires sporadically. Maybe 7/10. Sometimes it stops firing at all for some time. Even if I switch the light in the room on/off to the whole darkness. Although I see that MD is seeing the lux value correctly if I open the tuning window for this trigger while it is running. How nice it could be if this trigger could fire every time it has. Reliably.. Now I have to duplicate this function with the Regular Interval trigger, but it isn't nice.

Have you tried other automation apps? Such as Tasker, Automagic, E-Robot.