From 740cad9fc10cc4e3683b619cbe06da24ef18f1b0 Mon Sep 17 00:00:00 2001 From: tpearson Date: Wed, 18 Aug 2010 08:07:58 +0000 Subject: Attempt to fix incorrect meeting motices being sent when the first instance of a recurring meeting is deleted. This may need more work depending on how the number of recurrences are handled This should be more compatible with most CalDAV resources than the old way... git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/kdepim@1165076 283d02a7-25f6-0310-bc7c-ecb5cbfe19da --- korganizer/incidencechanger.cpp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'korganizer/incidencechanger.cpp') diff --git a/korganizer/incidencechanger.cpp b/korganizer/incidencechanger.cpp index 623eaa944..92332578c 100644 --- a/korganizer/incidencechanger.cpp +++ b/korganizer/incidencechanger.cpp @@ -82,7 +82,7 @@ bool IncidenceChanger::endChange( Incidence *incidence ) // FIXME: if that's a groupware incidence, and the incidence was // never locked, we can't unlock it with endChange(). if ( !incidence ) return false; -kdDebug(5850)<<"IncidenceChanger::endChange for incidence \""<summary()<<"\""<summary()<<"\""<endChange( incidence ); } @@ -289,7 +289,7 @@ kdDebug(5850)<<"IncidenceChanger::changeIncidence for incidence \""<sum int revision = newinc->revision(); newinc->setRevision( revision + 1 ); // FIXME: Use a generic method for this! Ideally, have an interface class - // for group cheduling. Each implementation could then just do what + // for group scheduling. Each implementation could then just do what // it wants with the event. If no groupware is used,use the null // pattern... bool revert = KOPrefs::instance()->mUseGroupwareCommunication; -- cgit v1.2.1