EAP version 1.24.0-dev

[Martin]

Variables in triggers is something that's under consideration, but I'm not sure how to implement it technically since global variables can be modified from a script so many triggers might need to be re-registered, which can cause some side effects. It might take some time until variables in triggers become possible...
The trigger Notification on Statusbar Selected has a button to list the actions that define a notification ID. What would you like to do with the list of IDs in the maintenance screen, just listing the action names?

[Martin]

A new EAP version is available.

Changes in this update:

• improved image quality of large notification icons displayed on an Android Wear device
• added possibility to add Android Wear actions in action Notification on Statusbar. Android Wear actions allow to specify a list of input values and/or voice input that can be processed in Automagic in variable input_value.
• added function convertNull to get the value of a variable or a default value when the variable contains null
• minor changes and fixes

Download: Automagic.apk (updated 2014-07-26)

BTW: Does anyone already own an Android Wear watch or is planning to buy one?

[kintrupf]

How is convertNull supposed to work? When I do “convertNull(someVar,true)“ I get an exception “
ch.gridvision.ppam.androidautomagic.simplelang.a.d: Could not convert value 'someVar' to boolean“

[kintrupf]

How is convertNull supposed to work? When I do “convertNull(someVar,true)“ I get an exception “
ch.gridvision.ppam.androidautomagic.simplelang.a.d: Could not convert value 'someVar' to boolean“

It seems I was to stupid
convertNull works fine, thank you!

[kintrupf]

The trigger Notification on Statusbar Selected has a button to list the actions that define a notification ID. What would you like to do with the list of IDs in the maintenance screen, just listing the action names?

I wasn't aware of that list. After months of intense use of Automagic I still find new things
That list is exactly what I was looking for, a list of the notification IDs and where they are used. You should add this list to the action Notification on Statusbar, so one can get an overview of already used IDs there.

In one flow I use Notification on Statusbar with a global variable as notification ID. The list only shows the name of the variable in curly braces, but not the value itself. That should be changed.

[kintrupf]

Variables in triggers is something that's under consideration, but I'm not sure how to implement it technically since global variables can be modified from a script so many triggers might need to be re-registered, which can cause some side effects. It might take some time until variables in triggers become possible...

I have no idea how triggers work internally, so I cannot advise you there. But I think triggers with variable support would be extremely useful!

Would it work to selectively re-register a trigger on demand? So after changing the trigger-variable we need to use an action like re-register trigger <trigger name> to update that one trigger to use the new value? Would that eliminate said side-effects?

While not an ideal solution it would enable us to create customizable flows with varying locations and such as triggers

[Martin]

Yes, a re-register action would work (or disable/enable the flow). This is one of the possibilities I had in mind, since it would also be clear what's happening within Automagic. On the other hand I have the feeling that most users would expect this to happen automatically when a variable is changed that's used within a trigger.

[kintrupf]

Yes, a re-register action would work (or disable/enable the flow). This is one of the possibilities I had in mind, since it would also be clear what's happening within Automagic. On the other hand I have the feeling that most users would expect this to happen automatically when a variable is changed that's used within a trigger.

That's right, many people would miss it and complain about a not-working trigger

But to prevent this...couldn't you just create a small, invisible flow with trigger Global Variable in the background which would disable/enable the original flow when the trigger variable changes? Wouldn't that work?

[bichlepa]

The functions getValue and setValue are not working anymore.
I get this error message when using getValue: "Fehler: Unsupported method getValue with 2 arguments."
My "Podcasts in car. Start" flow is not working anymore, as an exeample.

[Martin]

I can reproduce this problem. This should be fixed in the next EAP build.
Thanks for reporting!