[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-pim
Subject:    [Kde-pim] Single file resources create new collection when
From:       David Jarvie <djarvie () kde ! org>
Date:       2011-07-31 17:49:49
Message-ID: 201107311850.02586.djarvie () kde ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


The SingleFileResource base class does a clearCache() and synchronize() when it \
re-reads the backend file (e.g. if it is changed by an external process). This has \
the side effect that the resource's collection is removed and a new one created. The \
way I've coded things in KAlarm, this poses a problem, because KAlarm stores \
collection IDs to identify its calendars. If a resource changes its collection ID, \
this makes KAlarm  think that the calendar has been deleted, and a new one created, \
when all that has really happened is that the calendar's contents have changed.

Is there a good reason to create a new collection in these circumstances, or could \
this be changed to simply update the existing collection? If recreating the \
collection is really a good thing, what is a better way of keeping track of \
resources/collections within applications so that the link between a resource and its \
data isn't broken when this happens?

-- 
David Jarvie.
KDE developer.
KAlarm author -- http://www.astrojar.org.uk/kalarm


["signature.asc" (application/pgp-signature)]

_______________________________________________
KDE PIM mailing list kde-pim@kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/

[prev in list] [next in list] [prev in thread] [next in thread]