[Chandler-dev] Recurrence and changes to masters in the dashboard

[Bryan Stearns]

Jeffrey,

If the only attribute we're setting on the master that we should be 
setting on the occurrences, we could do either of these things:

- Observe 'read', and if it's set on a recurrence master, propagate the 
setting to all the occurrences when the observer fires

- Special-case recurrence masters in the code that sets the 'read' flag, 
and manually propagate the setting to all the occurrences if the target 
is a recurrence master.

(I prefer the latter: While it couples tighter, it seems lighter-weight 
than the former)

...Bryan

Jeffrey Harris wrote:
> Hi Folks,
>
> I'm working on bug 6702, "Clicking on recurring events in the dashboard
> doesn't mark them read".
>
> In fact, the events do get marked read, but it's their master event
> that's marked read (so read/unread applies to all occurrences).  This is
> the desired behavior.
>
> The problem is that changes to masters doesn't cause notifications to
> fire in the table.  I wanted to start a conversation on the list about
> how best to remedy this.
>