- 00Days
- 00Hours
- 00Mins
- 00Secs
-
Queue another event creates a brand new event every time you run that action. Queued events are just like standalone, regular events except on three points (if more, someone point them out). First, queued events don't require conditions if you don't want to put any. If you don't give it any conditions, queued event's actions always run, with or without a wait. Second, queued events don't have any advanced settings that regular events do, except for the delay-and-cancel action. Took me a while to understand this but giving a queued event conditions and a wait is equivalent to setting delay with cancel in regular events. If you don't set wait time in a queued event however, the queued event never gets canceled. Third, unlike regular events, queued events run only once then disappear. So, if you don't give a queued event any wait but give it some conditions, the queued event will never be canceled and hangs around indefinitely until all its conditions are met, its actions are triggered, then the event will disappear. This variation in behaviors gives you a great flexibility (or headache) in setting up some sophisticated events in rather simple ways. Besides, you can't call a separate condition-action event from inside of another event. You can call a shortcut to another event, but if you do that, the conditions of the event that's called are all ignored and the event actions always run.ok, understood. I solved my problem using the '(time)delayed switching off mobile data' method - temporary
.
Please let me one more question:
What is the main difference between the "Queue another event" and separated 'condition-action' event?
Inability of Llama to detect a process running in background seems to be a recurring problem for may people, especially with gps applications because Llama doesn't know whether gps is on either. The best I've come up so far is instead of turning gps off when an app stops or vice versa, I'd create a 'switch' that kills the app, gps, mobile data, and whatever else by a single tap. I'd figured, if you need tap tap tap to exit out of an app then gps, data, whathaveyou follow automatically, it would be as fast if not faster to tap on the kill button that takes care of everything.10-28-2014 03:49 AM - Feel free to hit that 'thanks' button
I remember kurokirasama writing similar things about queued events before, but it never made sense to me (the part that a queued event without wait will WAIT forever until all conditions are met) until I realize that a queued event MUST run once before being expunged. On the other hand, a queued event WITH wait gets canceled (and expunged) as soon as one of its conditions tests false, WITHOUT waiting for its wait time (hence, the same behavior as the delay-with-cancel action). It's very counter-intuitive and I wrote this here so I can find it later if I ever get confused again. I think the author of the app should change the term 'wait' to 'delay' to be consistent with regular events.
Anyways.
The kill switch idea for gps and apps is a bonus.10-29-2014 12:08 AM -
Yup youre correct sir, thanks for the input. Trying to talk with -113dBm is the same as no connection, unless you have a lte phone in an area covered by it (not my case)
EDIT: just learned that airplane mode won´t disable wifi
i'm so happy!
thank you for all the patience and the help given in this forum buggy_droid and raino11-22-2014 06:06 AM - Hello, synesthesiac. Cool trick.Google calendar already gives you an option to remind yourself before an event, up to few days, I think.
To make calendar reminders into alarms, I use this: CalendarAlarmHelper at Google Play store
Just realized that my answer doesn't involve Llama at all...
Well, about half the stuff I say here don't, eitherWhy not create a calendar event by GoogleNow instead?
Then whatever alarm/reminder app you are using will pick up on the calendar event.
Once again, Llama has run out on me here.11-29-2014 09:47 PM
