Bug 106400

Summary: Recurring multi-day appointments not displaying correctly in month view
Product: [Applications] korganizer Reporter: MG <metro_guy01>
Component: generalAssignee: Reinhold Kainhofer <reinhold>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Slackware   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description MG 2005-05-28 02:49:28 UTC
Version:            (using KDE KDE 3.3.2)
Installed from:    Slackware Packages
OS:                Linux

Multi-day recurring appointments not displaying correctly in month view
Note: this works fine for non-recurring multi-day appointments

I'm running KDE 3.3.2 on Slackware 10.1

Steps to reproduce:

1) Select a day by in month view e.g. 6-6-2005
2) Double click and bring up dialog box
     Enter "title" data
     Select end date 6-8-2005   (3 day duration)
3) Click on "Recurrence" tab
     Check "Enable recurrence"
     Leave everything else as is 
4) Click "Apply" and "OK"

Result:
 -- Recurrence is shown correctly, 
 -- Start day indicator with title is shown correctly i.e. "(-- title"
 -- No end-day indicator is shown i.e. "--)" is not displayed


Now repeat the above steps but do not make it a recurring appt

Result:
The multiday appointment is displayed correctly with "(--"  AND  "--)" indicators

Anyway, keep up the good work guys. Korganizer is awesome and I use it all the time.
Comment 1 Bram Schoenmakers 2005-05-31 23:23:58 UTC
I think this bug will be automatically solved once I've ported KoPI's monthview to KOrganizer. So I won't have an immediate look at this bug.
Comment 2 Reinhold Kainhofer 2005-07-23 11:26:15 UTC
As bram said, the problem might be solved by Lutz' KO/Pi patches. Anyway, this is not restricted to the month view. The week view, for example, is also not able to show recurring multi-day events correctly.
This problem is already known as bug 42899 (the original report is misleading, becaus midnight should not belong to the next day! But the other comments treat that problem).

Cheers,
Reinhold

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