Mimi,
Our recurrence implementation doesn't allow individual occurrences to
have their own values for attributes (that is, values different from the
master's) unless the occurrence is a "modification", which means it
inherits *no* attributes from the master (and won't change if an "all
events" or "this and future" modification is made to the series).
(Alternatives to this have been proposed, but aren't going to be
implemented soon.) ... so (see below)...
Mimi Yin wrote:
Hi Bryan,
On Sep 12, 2006, at 3:47 PM, Bryan Stearns wrote:
Grant interprets the spec (I think) to call for showing
modifications. However, I'm not sure what constitutes a modification.
Philippe suggested, and Mimi +1'd, that triageStatus changes should
be considered modifications, but triage status changes with the
passage of time, so every event that's gotten bumped to Now and is
now in the past would be a modification.
I think the user has to manually set an event from NOW to DONE. It
doesn't automatically become DONE just because the event end date/time
is in the past.
Right - but when an event's startTime is reached, it automatically
becomes "now", which doesn't work right for recurrence series because
occurrences can't have their own attribute values without becoming
modifications.
(Yesterday, I got fed up with thinking about these recurrence issues,
so I implemented the mechanism to set the "read" attribute when an
item is displayed in the detail view - it works great for ordinary
items, but guess what happens when you display a recurring event? You
get the All/This/ThisAndFuture alert, and get to create
modifications. Clearly that's wrong: even if we didn't put up the
alert, it'd mean that any occurrence you've looked at suddenly became
a modification!)
It might make sense for individual instances to be Read or Unread. For
example, if I edit and update the Agenda for the 3rd instance of a
weekly lecture series and send it to you, shouldn't you see that
particular instance of the recurring event as unread?
Except that individual occurrences can't have their own attribute values
without becoming modifications.
Although now re-reading what you wrote, I'm not sure I understand what
you mean by: "any occurrence you've looked at suddenly became a
modification".
...Bryan
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
