Subtle changes

Jacob L

Moderator
Just wondering if these few changes would make it easier for new and existing users.

1) Default variable as string. Currently the default for local variables is Boolean, I don't know about others but more of my use cases are using string variables so if it were string by default it is one less click (or 5+ if you created boolean instead of string by mistake).

2) Search magic text, it might be easier to find what we are looking for, however I am starting to memorise some of them.

3) Local variables at the top of magic text, they are currently under global variables, but it might be easier to find if they are at the top? Also Maybe alphabetical order would help. It also took me ages to work out what 'power on/off' meant but it is if device is plugged in or not.

4) trigger as magic text, for example I set a variable as triggered by call followed by a variable set triggered by SMS and constraints to check before setting. It would be more efficient to just store the trigger in the magic text and set variable once than set it twice with constraints.

5) Be able to remove our own plugin suggestions, I have added apps to the plugin store which are no longer plugins but they are still in and I cannot remove them so I could accidentally confuse people.

6) Notifications on comments would be amazing so that we know when our macro has a new comment.

7) Ability to change our store username, now my name is inconsistent but it is a minor thing.

8) Macro update notifications so that if a macro we use or starred gets an update, we can be notified. This is important for those who need bugs fixed in the macros
 

FrameXX

Well-known member
2, 3, 5, 6, 7, 8 totally agree. Would be really useful.

About 1 I would say that if you are learning with variables you are propably going to start with booleans to make MacroDroid just remember something basic and they are also the simplest ones. Adding the settings to change default would be nice, but really a detail.

I don't understand 4.
 

Jacob L

Moderator
don't understand 4.
If I had multiple triggers and wanted to find which fired, then I have to set variable per trigger and use constraints to say only set variable if x trigger fired. Having 3 triggers needs 3 set variable actions and 2 or 3 constraints. Then the macro gets big and complicated unnecessarily
 

Jacob L

Moderator
About 1 I would say that if you are learning with variables you are propably going to start with booleans to make MacroDroid just remember something basic and they are also the simplest ones. Adding the settings to change default would be nice, but really a detail
Learning doesn't make any difference. String can hold numbers and letters so by setting it as default it is easier than changing from boolean which I hardly use
 

Jacob L

Moderator
These are some other changes that would help us:


Link to user profile would be useful as well.

Action to clear MacroDroid's own cache

Colours for display dialog action

Delete empty categories action

A tab for macros we have put a star on
 

420

Active member
Learning doesn't make any difference. String can hold numbers and letters so by setting it as default it is easier than changing from boolean which I hardly use
I think it does make a difference, surely when you just started using macrodroid you did not start by using string variables right away?

I feel the way it works now makes the most sense, the way i see it boolean's are the basics and if you want something more complicated you simply have to perform a couple extra steps, this really makes perfect sense to me.

I think having an option to change the default (for more advanced users) is a not a bad idea though! (y)
 

tanutanu

Well-known member
I agree with @Jacob about the order of variable data types. String data type is most frequent to use. Tab style dialog or category filter like on the system log view is also helpful. As @420 said, at least variable filtering search is required on the variable dialog.

I also want floating tool box on actions field. When I move a specific code block, I have to go to the top and press the reorder button once, then get back and take a if statement like a 80 yard super long pass on soccer or football games. Or put the statements of the block in dummy if/endif once, then copy and paste it.
If the tool box is floating style, we can access the reorder button wherever editing. I use almost all options via context menu excluding reorder sometimes, but newbies tend to do via graphical icons. And if the box has full text search, it should be more powerful.
 

tanutanu

Well-known member
Changing variable data type is also helpful. I often make a variable as boolean mistakenly, so have to delete once and make it again as string or integer.
If the variable has value when changing, the type cast rule might be same as Java's. string to integer is ok when numeric but impossible the others, i.e. A to Z, simply catch the number format exception and set to 0(zaro).
 

Jacob L

Moderator
I think it would be useful to be able to copy if statement conditions.

[this macro] also appears at the bottom of the list on notification buttons and it would be better at the top.
 
Top