nstoker
-
7 votesdeclined ·
AdminCarter
(Admin, two forty four a.m.)
responded
While I see the potential usefulness of this, Locale is designed to be an app that runs in the background and works as unobtrusively as possible. Popping up a dialog every time a situation changed would be incredibly annoying for most users! In addition, most users aren’t looking at the phone when a situation change occurs (e.g. the phone is in your pocket when your location changes), so situations might not ever change.
Are there any compelling use cases for this feature request?
As an alternative, if you want to temporarily disable Locale, that can be accomplished under the Menu of the main Locale screen.
nstoker
gave this 1 vote
·
-
10 votesplanned ·
AdminCarter
(Admin, two forty four a.m.)
responded
Good idea! This will be implemented once the UserVoice website becomes mobile friendly. In order to make that happen, consider adding some votes to UserVoice’s own forum here http://feedback.uservoice.com/forums/1-product-feedback/suggestions/143027-develop-a-mobile-iphone-optimized-site?ref=title
nstoker
shared this idea and gave it 1 vote
·
-
477 votescompleted ·
AdminCarter
(Admin, two forty four a.m.)
responded
At long last Locale 3.0 introduces the Calendar condition to detect events on your Google Calendar, Exchange Calendar, or any other calendar supported by Android.
While Locale 3.0 is available for Android 2.2 or later, the Calendar condition requires Android 4.0 or later. To learn more about Locale 3.0, please see our release notes here http://blog.twofortyfouram.com/post/19303488607/locale-3-0
nstoker
gave this 1 vote
·
-
79 votescompleted ·
AdminCarter
(Admin, two forty four a.m.)
responded
This is now supported with the combination of Locale 1.0 and the “Locale Headphones Plug-in”, both of which are available on the Android Market in countries that support paid apps.
Locale 1.0 supports plug-in conditions, so many more exciting features are coming soon :)
A plug-in to control media volume will be released in the near future :).
nstoker
gave this 1 vote
·
Carter - I agree with raynerape that he most probably means (2). I'm voting for this on the basis of it being (2). But good work for picking someone up for being ambiguous with a request! :-)