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

List:       kde-pim
Subject:    Re: [Kde-pim] Why does Korganizer not like December 22?
From:       Eugene Nine <enine () ninefamily ! com>
Date:       2003-12-22 18:18:42
[Download RAW message or body]

On Monday 22 December 2003 10:47 pm, Mark Bucciarelli wrote:
> On Monday 22 December 2003 12:36 pm, Eugene Nine wrote:
> > Hmm I closed and reopened Karm and it seems to have fixed the problem.  I
> > compiled Karm from CVS to fix bug 70797.  Then I added a few entries to
> > korganizer today.  I timed the update and it was 5 minutes which is the
> > time karm saves and korganizer reverts back to an earlier copy.  I closed
> > Karm and opened it again and the problem went away.   I did have a couple
> > crashes with korganizer earlier, may be related.
>
> I knew this was going to happen.
>
> You have KArm and KOrganizer pointing at the same file, right?
>
> There is currently no locking implemented--KArm and KOrg clobber each
> other. I better fix this pre-3.2 or we will get a ton of bugs or people
> will just think things don't work right.
>
> Regards,
>
> Mark
> _______________________________________________
> kde-pim mailing list
> kde-pim@mail.kde.org
> https://mail.kde.org/mailman/listinfo/kde-pim
> kde-pim home page at http://pim.kde.org/  
Yep thats it.  How do other apps handle it, kconsolecalender for example.  
Would it be a worthwhile idea to make the libkcal layer work like a service 
and all the front ends send messages to the klibcal layer instead of writeing 
to the file?
_______________________________________________
kde-pim mailing list
kde-pim@mail.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]