FrameXX
Well-known member
Recently there was added ability to select app to launch via package name that could be variable. I appreciate that, but i think that lot of more MacroDroid triggers, actions, and constrants need this ability to be configured with variables as they are most static now, and limits user ability to make really dynamic macros (there is always way how to make macros more "dynamic" with separate constraints but in a lot of cases it takes a lot more effort and macro is more complicated, harder to manage, orientate in... than it would have to.)
So i am making here a list of triggers, actions, and constraints, that i think most need variable integration and i find it missing there. I am really not going to write every block where variable integration could be done, since I personally didn't find any need to use variable that would I miss in lot of them.
As lot of these blocks choose from multiple apps, I would separate every app package with comma or space.
So i am making here a list of triggers, actions, and constraints, that i think most need variable integration and i find it missing there. I am really not going to write every block where variable integration could be done, since I personally didn't find any need to use variable that would I miss in lot of them.
- App Install/Remove/Update - ability to choose packages that could be variables.
- Application Launched/Closed - same...
- Notification - same...
- Light sensor - ability to work with current light level as MacroDroid decimal variable.
- App Enable/Disable - ability to choose packages that could be variables.
- Clear App Data - same...
- Kill Application - same...
- Kill Background Process - same...
- System Setting - ability to use variables in "value" field.
- Application Running - ability to choose packages that could be variables.
- Volume level - ability to use integer variable as volume level.
As lot of these blocks choose from multiple apps, I would separate every app package with comma or space.