AndCycleAndCycle

  1. 21 votes
    Vote 0 votes Vote Vote
    Vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service

      You'll receive a confirmation email with a link to create a password (optional).

      Signed in as (Sign out)
      You have left! (?) (thinking…)
      declined  ·  CarterAdminCarter (Admin, two forty four a.m.) responded

      As I understand it, the only reason for this request is really for reusing a condition or setting across multiple situations. Given that most conditions or settings are very easy to set up individually, the value gained by re-use seems low unless the number of situations is on the order of 10 or more.

      We experimented with reusable Locations in older versions of Locale, and found the UI to be exceedingly complex and the benefits of reuse didn’t offset the UI complexity required.

      AndCycleAndCycle gave this 3 votes  · 
    • 91 votes
      Vote 0 votes Vote Vote
      Vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        I agree to the terms of service

        You'll receive a confirmation email with a link to create a password (optional).

        Signed in as (Sign out)
        You have left! (?) (thinking…)
        under review  ·  CarterAdminCarter (Admin, two forty four a.m.) responded

        This is a great idea and we’ve been looking at it for quite a while. I agree it could be quite useful when combined with Astrid integration. For example, a location-aware reminder would be really useful a few minutes after arrival, rather than right when walking in the door.

        A key requirement would be that the delay should be very consistent and predictable. For example, if I ask for a reminder 30 minutes after I get home, it should always be exactly 30 minutes after I get home. Thanks to Locale 2.0’s instant location, we are now be able to meet this requirement.

        I have a few open questions about this as we go forward with investigating how this might work:

        - Should there be delayed conditions? Or should this be implemented as delayed settings? (The end result would be the same, but each requires a different mental model) -… more
        AndCycleAndCycle commented  · 

        agree with this one, tasker have similar function called cool down time,
        this will be useful to prevent profile repeat it self in short time,

        although there is a plugin called "Locale Timer Plug-in" by DroidMunkey LCC,
        it's not working at all and the company seems abandoned all their developed plugin,
        this is really frustrated.

        AndCycleAndCycle commented  · 

        agree with this one, tasker have similar function called cool down time,
        this will be useful to prevent profile repeat it self in short time,

        although there is a plugin called "Locale Timer Plug-in" by DroidMunkey LCC,
        it's not working at all and the company seems abandoned all their developed plugin,
        this is really frustrated.

        AndCycleAndCycle commented  · 

        agree with this one, tasker have similar function called cool down time,
        this will be useful to prevent profile repeat it self in short time,

        although there is a plugin called "Locale Timer Plug-in" by DroidMunkey LCC,
        it's not working at all and the company seems abandoned all their developed plugin,
        this is really frustrated.

        AndCycleAndCycle gave this 3 votes  · 

      Knowledge Base and Helpdesk