Bug 72770 - Recurrent event spawning in two days does not show after the week it was defined in
Summary: Recurrent event spawning in two days does not show after the week it was defi...
Status: RESOLVED DUPLICATE of bug 42899
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: 3.1.1
Platform: Compiled Sources NetBSD
: NOR normal
Target Milestone: ---
Assignee: Cornelius Schumacher
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-16 18:38 UTC by Julio M. Merino Vidal
Modified: 2004-01-17 18:29 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Julio M. Merino Vidal 2004-01-16 18:38:23 UTC
Version:           3.1.1 (using KDE 3.1.4)
Installed from:    compiled sources
Compiler:          gcc version 3.3.2 (NetBSD nb1 20031026)
OS:          NetBSD (i386) release 1.6ZG

Lets start by creating an event that spawns two days.  In my case, it starts on 23.30 Thursday and ends on 1.30 Friday.  Now, enable recurrence on that event, for example weekly.  After that, confirm the event so that it gets added to the table.  You can see it correctly in the current day, and if you switch to the next day, you can see the second half of it.

Now, advance the table view a week.  The event has disappeared.  Note that this only happens when you are in daily, weekly, work week, and 3 days views.  If you switch to the monthly view (which seems to be using a different widget for drawing), you will see your event defined properly in all weeks.  So, the event is kept by the program, but it's not shown properly.

Furthermore, if you attach an alarm to it, say 5 or 10 minutes before, it will be fired properly, even if you can't see the event in that concrete week.
Comment 1 Reinhold Kainhofer 2004-01-17 18:29:50 UTC
Yes, korganizer isn't able to show recurrences on multi-day events correctly. For more information, see bug 42899.

Thanks for your bug report,
Reinhold

*** This bug has been marked as a duplicate of 42899 ***