I guess it is normal as Selection dialog is made to return either a number or a text corresponding to the selected item.I see that selection dialog doesn't save any value to decimal variables, I do not know if this is intended
Then it should disallow saving to decimal variablesI guess it is normal as Selection dialog is made to return either a number or a text corresponding to the selected item.
You're probably right.Then it should disallow saving to decimal variables
the problem also exists in version 5.33.5it seems that "identify in the application" doesn't work, at least he doesn't click on the ID (Home Screen, Back, Last opened) in version 5.33.4
I see what you mean: it's possible to select a decimal variable to store the number of the clicked item.Then it should disallow saving to decimal variables
It should save correctly into a decimal, so I will fix this in the next beta.I see that selection dialog doesn't save any value to decimal variables, I do not know if this is intended
What was the problem? I think the best way to answer your question would be... to check itHi, is the compare values contraints for trigger section fixed?
Nevermind, I just tested it on latest 5.33.6 & it's working fine now. Moreover, feel much smoother & responsive than 5.32.8 in macro execution.What was the problem? I think the best way to answer your question would be... to check it
https://www.macrodroidforum.com/ind...-selected-notification-title.4215/#post-24927@alexhee Can you post the issue here, or a link to your original post. I have 100s of things going on so I don't even remember what the issue you are talking about is at this point.
Thanks for your quick response. I just reported the issue to you.@alexhee I've taken a quick look at this and it's not clear how Invoked/Not Invoked constraint is related to your previous issue, so I'm not sure exactly what I'm looking for.
Could you please submit the simplest macro you can then demonstrates this issue via the report a bug feature in the troubleshooting section and I will take a look.
@egorver Thanks for flagging this issue, I've spotted the cause and will get a fix out soon.
Oh dear, looks like it works for the x location but I screwed something up for the y location. Fix incoming....Thanks for the quick response! Problem solved, but only for LOCAL variables. Click using GLOBAL variables still doesn't work.