[Kde-pim] korganizer doesn't save resources immediately when changed or deleted (bug 143511)

[David Jarvie]

On Wednesday 28 March 2007 13:49, Reinhold Kainhofer wrote:
> Am Mittwoch, 28. März 2007 schrieb Adriaan de Groot:
>> On Wednesday 28 March 2007, Brad Campbell wrote:
>> > Another option perhaps is a dcop signal to indicate that something
>> else
>> > is going to want an accurate snapshot of the calendar to cause
>> korganiser
>> > to properly save and clean up?
>>
>> Unfortunately KOrganizer's DCOP interface is a hodge-podge of methods
>> with
>> little consistency and it's missing, in particular, a "save now"; that
>> means that any user of that *new* method would also have to be prepared
>> to
>> have the call fail because it is talking to an older korganizer.
>
> It's not only korganizer. Such a dcop would need to be in libkcal to make
> sure
> that other applications using libkcal will also save (e.g. knotes, karm,
> kalarm, etc.).

FWIW, kalarm saves its resources after each change. I decided that this
was a good policy anyway in case of crashes or whatever, but in addition
live alarms have to be saved in order for the alarm daemon to see the
update. But kalarm is unlikely (AFAIK) to have calendars as large as
korganizer might, so it's less likely to suffer from any performance
problems due to parsing the calendar.

-- 
David Jarvie.
KAlarm author & maintainer.
http://www.astrojar.org.uk/kalarm

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