The original request here was for a logical NOT operator, although it doesn’t make sense to create a logical NOT operator in Locale. Most of the time, NOT isn’t the right way of thinking about a Condition. For example, NOT 9 am to 5 pm could be redefined as 5pm to 9am. NOT at work would simply be the Default situation. For the other conditions built-in to Locale, thinking about the problem in a different way usually means that NOT isn’t needed. If a Condition truly needs NOT logic, then that should probably be put into the individual Condition’s UI itself rather than as part of the Edit Situation screen in Locale.

Although this request is for a NOT operator, I believe the underlying request here is a way of detecting the transition between situations. The strongest use case would be detecting when you’ve left a particular Location. While Locale can easily detect the transition between situations, providing a UI to allow the user to do something with that transition is extremely complex.

Today, Locale treats situations as a continuous event. When Locale determines that a situation is active, it applies that situation’s settings. When leaving a situation, a lower priority situation’s settings take precedence (usually the Defaults). This provides a single, consistent behavior that makes Locale easy to understand.

One suggested implementation is to have “On Enter” and “On Exit” settings within a situation. On Enter settings would work like the current settings within Locale, while On Exit would be applied when leaving a situation. But what if the On Exit settings of a situation are in conflict with the On Enter settings of a higher-priority situation? The number of arrangements that the user must think about has just doubled.

We’re still evaluating ways to solve the underlying requeste of “leaving a location”, without making the UI too complicated…

UPDATE:

Locale 1.4 includes significant improvements to the location detection system, reducing time to detect location changes by 20% while also improving battery usage by up to 50%.

The original goal of this request—reducing the delay of detecting location changes—has been met as Locale 1.4 detects location changes within an average of 4 minutes. We are therefore marking this request as completed.

Although this request is being marked as completed, we have ongoing research and development to keep improving the speed and efficiency of the location detection system further :).

(Original response)

By design, Locale has no user-configurable options. The goal is that Locale should “just work” without requiring users to fiddle with various options that could negatively impact the operation of the app. For example, asking Locale to check location every minute could cause the battery to drain within 2 hours at which point you might miss the train stop anyway.

Although a user-configurable option won’t be implemented, I see the underlying goal as improving how quickly Locale detects that location has changed. For Locale 1.3 and earlier, it can take up to 10 minutes for location changes to be detected.

I’m therefore repurposing this request for implementing improvements to the speed of the location detection system. Once these improvements are completed, a user-configurable update frequency will no longer be necessary.