Location inverse

[Lowell]

Any particular reason why we can't have an inverse option for
Locations, similar to states? I'm migrating from Setting Profiles,
and that's a feature I used for many of my conditions that I'm having
trouble moving over to Tasker. I'm finding that trying to use exit
tasks for a location doesn't accomplish the same thing, and is very
different than defining a condition as (at least in part) being not at
a particular location.

Can we add inverse locations?

[Richard Hodgson]

You could possibly do this by adding a location event, and only adding an Exit Task, although I've not tested it.

[Lowell]

Actually-- I have figured out another workaround. If I set a profile
with the context of a particular Location, then set the task to set a
variable, then I can key other contexts off of the value of that
variable. As such, I can create "not at Location" tasks by checking
for the value of the variable set by that particular location....

However, this would be a lot simpler if I could just create an inverse
location context.

-Lowell


On Aug 13, 11:12 am, Richard Hodgson <richard.hodg...@gmail.com>
wrote: