SHAWON
Member
Can't set position with variable in Floating Text action. Is this a bug?
v5.50 - Feedback
- Thread starter MacroDroidDev
- Start date
- Status
SHAWON
Member
Correct, I thought it was pixel resolution. thanks
Endercraft
Moderator
Try to set shake sensitivity to a lower value (settings -> trigger options -> Shake trigger).
The lowest value is always set. I use this feature for a long time in my project, but this strange behavior has began the last time about since 4.49.13
The difficulty is I cannot reproduce it reliably to understand. But in the log I see this shake happening while I didnt do any shaking. Since my project uses the shaking to manage the phone calls, I can see this unpredictable behavior very clearly.
The problem may be connected somehow with the background working of this trigger. I use this mode while phone call is going on. Just to make sure that it will fire anyway if the screen is off and the power button was pressed before. The shake trigger is incorrectly fired after I place the phone to my ear. It didn't do this about a year I use the feature. Something's been changed.
May I say here that currently MD does array manipulation in a wrong way when doing a reverse operation?
It does not only reverse but may do reordering too.
Example: an array (ab, cd, ef, gh, 234, ac, 123) after reverse becomes (123, 234, ac, gh, ef, cd, ab) that is obviously wrong for a reverse operation. So, after 2 times array reversing you get not the same initial array as expected: (ab, cd, ef, gh, 234, ac, 123) -> (ab, cd, ef, gh, ac, 234, 123). It does unpredictably break the array.
Can Dev fix it in the beta?
It does not only reverse but may do reordering too.
Example: an array (ab, cd, ef, gh, 234, ac, 123) after reverse becomes (123, 234, ac, gh, ef, cd, ab) that is obviously wrong for a reverse operation. So, after 2 times array reversing you get not the same initial array as expected: (ab, cd, ef, gh, 234, ac, 123) -> (ab, cd, ef, gh, ac, 234, 123). It does unpredictably break the array.
Can Dev fix it in the beta?
@GamBIT Once again thanks for reporting this issue and I now have a fix ready for the next beta (which will be soon).
I'd like to ask one more time to please use the report a bug option in the troubleshooting section for issues like this. It really makes my life a lot easier to track and fix bugs because I have good processes in place for bugs reported this way and it saves me having to manually manage things (which can lead to things getting forgotten).
I'd like to ask one more time to please use the report a bug option in the troubleshooting section for issues like this. It really makes my life a lot easier to track and fix bugs because I have good processes in place for bugs reported this way and it saves me having to manually manage things (which can lead to things getting forgotten).
AkashiDom
Active member
Last edited:
If so I would remind you about the previous similar bug of the wrong sorting method 'ABCDE...abcde...'. It is an important issue as this one, I guess.
And the variable renaming issue, where this renaming would not be done everywhere in macros, leading to break the macros logic.
p.s.
Could it be a good idea to make a branch in this forum for the bug reports? 'Bug Reports'.
People would report with the examples, others would comment, nothing would be lost and You could mark that themes as important to You (to fix the bug). It would be very visually to the people and handy in use.
Last edited:
AkashiDom
Active member
Use Help and Troubleshooting since we're discussing about bug.
It's not the same I was talking about.
AkashiDom
Active member
Help and Troubleshooting is place when you having issue with MacroDroid. As in the description:
Incase of some bug being hard to reproduce, you can use that Forum to request assistance from the others if they had the same experience.
Alternatively, you can post a thread in General MacroDroid Discussion to discuss about something else related to the bug. But it is recommended to post it in Help and Troubleshooting.
Besides, Report a Bug button is in the Troubleshooting panel and the forum name is Help and Troubleshooting.
I think you confuse a bug report with some asking questions like 'Huston, we've got a problem!' etc. A bugreporter doesnt ask 'what it was?' or 'is it a bug or a feature?' or 'help me, what to do?!'. A bugreporting message means a bugreporter does understand a problem, does show it even with the examples. Troubleshooting assumes the user doesn't understand the problem.
AkashiDom
Active member
I don't want to quarrel. You don't understand what I mean so that's that. If want example, it's this thread.
Last edited:
Please stop procrastinating with @MacroDroidDev. He has so much more interesting and important job to do than arguing with you...
Please stop the inattentive reading. I was talking to AkashiDom. I've got much more interesting things to do than responding to your attacks.
LinerSeven
Well-known member
Hi, @GamBIT,
You may feel differently, but We 're not making any attacks against you. Rest assured.
Of course, we understand that you want to share the challenges you have with those around you and seek solutions as a priority.
However, they don't need to be carried out in a beta thread, where people dare to overreact, and I am suggesting that they be discussed in a separate thread to make it a fair communication with the developers and others.
Please understand.
Best Regards,
Liner Seven,
You may feel differently, but We 're not making any attacks against you. Rest assured.
Of course, we understand that you want to share the challenges you have with those around you and seek solutions as a priority.
However, they don't need to be carried out in a beta thread, where people dare to overreact, and I am suggesting that they be discussed in a separate thread to make it a fair communication with the developers and others.
Please understand.
Best Regards,
Liner Seven,
- Status