Katie Capps Parlante wrote:
Bryan, do you want to weigh in on the "bring private collection back" option?
OK, so as I understand it, per-item notification isn't planned for 0.6 (it will "go on the list [for 0.7] if it doesn't make it on 0.6"). Until it does, I think we should leave monitor-based notifications on individual attribute editors as they are, and not worry about bugs relating to changes arriving from other views (ie, via sync - this was use case E in my original message).
That leaves whether (and how) to fix use case F (user changes a non-first occurrence of a recurring event to 'once', thus deleting the displayed item); the primary way we've talked about this is to use a private item collection (off the branch-point/trunk-parent block right above the DV), and use its notification to find out when the item is deleted. I think this is small and safe enough to do for 0.6.
OK, Katie? ...Bryan _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
