Hi Keith, > Example: our ageing grandfather clock needs winding every 6 days. In > DateBk, this is set up as an event repeating every 6 days, with a tick > in the 'from check off' box. If I can't do it on the day, the overdue > event continues to have 'Now' status until I get round to doing it, at > which point marking it as done generates a repeat in six days time from > /now/. > > This is ideal for those things that have to be done at regular > intervals, but that can slip for a day or two: give cat worm tablet, > check car tyre pressures, do monthly review, etc, where, having slipped, > you don't want to go back to the original schedule.
Other examples of this sort of task: oil changes, cleaning the house, watering plants. I've heard a few requests for this in the past, but I don't think we've heard it from outside OSAF yet. Thanks for describing the problem so clearly! I'm not sure how exactly we'd implement this in the UI. Under the hood, it would involve recurrence changes, which tend to be tricky, we'd have to figure out how we'd share these. But it does seem like a good idea. > PS Can't believe how useful even 0.7 is - it just sort of works how I do! That's very gratifying, thanks! Sincerely, Jeffrey _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
