Hi.
Thanks for the feedback. Really appreciate it.
Well well well... I never tested "location" as a constraint and it is actually the logic I was after: "inside or outside" some area (or all areas) instead of "entered or exited" some area (as in a position change logic).
As I said, I changed the macros to use your own implementation and now everything works the way I want. Just perfect. Location as a constraint opens up new possibilities because of the logic it implies. GREAT!
I'm sorry about the "macros no longer run" misconception. What I meant was that they don't run (execute) because of the location test result, nothing more. The thing is that after reviewing the system log, I found that Geofence would update inconsistently (and later confirmed by your comment in this thread) and test every geofence set up, so the phone might be in a second defined geofence by the time the location updated and this was the problem:
The global variable was set to false if the phone was outside any area, set up as trigger "
exited area". Then the system log showed that "entered area 2" (where the phone was) would set the variable to
true correctly, and then immediately evaluate "area 1" as "
exited area" effectively setting the variable back to
false. I hope this makes more sense.
Best regards.