Please bump up the priority of this a bit.
Having a "removeVariable" function which is not able to remove global variables is a bit pointless, since local variables are automatically deleted when a flow ends...
Search found 257 matches
- 09 Jan 2014 14:14
- Forum: User Help / Bug Reports
- Topic: Deleting Global Variables
- Replies: 4
- Views: 10715
- 09 Jan 2014 12:38
- Forum: User Help / Bug Reports
- Topic: Volume values from "Init variable system setting"?
- Replies: 3
- Views: 10220
Volume values from "Init variable system setting"?
When I use the action "Set Audio Volume" to set the ringer volume to 0 I would expect that afterwards the action "Init variable system setting" (name=volume_ring) would return 0. The status bar indicates that the volume is indeed muted. However, on my phone (Nexus 4, KitKat 4.4.2) this action always...
- 09 Jan 2014 11:56
- Forum: Feature Requests
- Topic: Prefix for variables for "Store/Restore Audio Volumes
- Replies: 0
- Views: 5784
Prefix for variables for "Store/Restore Audio Volumes
Right now the actions "Store Audio Volumes" and "Restore Audio Volumes" always use the same set of global variables. So it is not possible to have several independent sets of volume variables for different flows nor is it possible to have "local" storage of that values only within a flow to save the...
- 09 Jan 2014 11:40
- Forum: Feature Requests
- Topic: Action "Store Audio Volumes" should have checkboxes for type
- Replies: 0
- Views: 5429
Action "Store Audio Volumes" should have checkboxes for type
The action "Restore Audio Volumes" allows me to restore only certain types of sound with 7 checkboxes, of which I usually check only 3.
However, the action "Store Audio Volumes" always saves all 7 global variables. IMHO almost always they are not all needed and only clutter the global variable list.
However, the action "Store Audio Volumes" always saves all 7 global variables. IMHO almost always they are not all needed and only clutter the global variable list.
- 09 Jan 2014 11:35
- Forum: Feature Requests
- Topic: Action "Set Audio Volume" should support variables
- Replies: 1
- Views: 6385
Action "Set Audio Volume" should support variables
Right now one can only select a fixed volume with the slider.
- 06 Jan 2014 13:25
- Forum: Feature Requests
- Topic: Trigger: Bluetooth device nearby
- Replies: 12
- Views: 37248
Re: Trigger: Bluetooth device nearby
brunofin, take a look at the newest version of Automagic from the "EAP - Early Access Program" section of this forum. This new version supports the new trigger "User Activity (Experimental)" which will trigger when you are moving in a car. I use this new trigger to enable bluetooth, and for the past...
- 06 Jan 2014 10:16
- Forum: Flow Sharing Area
- Topic: Disable screen timeout while App is running
- Replies: 0
- Views: 6965
Disable screen timeout while App is running
Very often my default screen timeout switches off my display while I'm studying a flow or "mentally debug" it. So I deciced to remedy this by creating a flow that will disable the screen timeout while Automagic App is active in foreground and resetting it to 30 seconds when it is closed. Adapting th...
- 06 Jan 2014 08:41
- Forum: Feature Requests
- Topic: Support variables in action "Set Screen Timeout"
- Replies: 0
- Views: 5587
Support variables in action "Set Screen Timeout"
The action "Set Screen Timeout" should support variables, so that I could reset the timeout to some previously saved value. I guess The action "Init Variable System Setting" with value SCREEN_OFF_TIMEOUT should return the current timeout setting. My device returns the value 86.400.000 for a 30 secon...
- 05 Jan 2014 11:23
- Forum: Feature Requests
- Topic: Name of currently executing flow as varibale
- Replies: 1
- Views: 6678
Name of currently executing flow as varibale
For logging purposes and such it would be great it the name of the executing flow would be always available as a default flow variable like "triggertime". I would suggest "flowname" or "currentflow" as the name of that new variable. If a flow is executed from another flow with the "Execute flow" act...
- 05 Jan 2014 10:53
- Forum: Feature Requests
- Topic: Execute flow as "procedure" with parameters
- Replies: 4
- Views: 15837
Execute flow as "procedure" with parameters
I'm using some flows as "procedures" in other flows with the "Execute flow" action. This works very well, but it is a bit cumbersome to pass arbitrary variable values to the "sub"-flow. To do this I need to define one or more local variables with additional "Script" actions before I use the "Execute...