Request trigger Location improvement
Posted: 25 Nov 2016 15:21
Think about when you stay home for 10 hours. Sometime the google location may get position far away from where you are (low accuracy). These behavior will trigger the exit event.
So, If the exit/enter event occur, you can request a new location with high accuracy.
Is it good if you can add in the internal code before fire the event?
And the radius will work very high accuracy too. And we don't need the addition task to check the real distance.
Currently, I tried by myself. The trigger will run twice when google position is invalid or low accuracy.
1. Trigger Location : do exit event when google position is invalid and far away.
2. Action Init Variable Location : request new high accuracy.
3. Trigger Location : do enter event when google position is valid again (from #2).
So, If the exit/enter event occur, you can request a new location with high accuracy.
Is it good if you can add in the internal code before fire the event?
And the radius will work very high accuracy too. And we don't need the addition task to check the real distance.
Currently, I tried by myself. The trigger will run twice when google position is invalid or low accuracy.
1. Trigger Location : do exit event when google position is invalid and far away.
2. Action Init Variable Location : request new high accuracy.
3. Trigger Location : do enter event when google position is valid again (from #2).