Bug 104729 - no time in month view when event crosses day boundary
Summary: no time in month view when event crosses day boundary
Status: RESOLVED FIXED
Alias: None
Product: korganizer
Classification: Applications
Component: monthview (show other bugs)
Version: 3.4
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-28 20:51 UTC by Richard Bos
Modified: 2009-01-07 13:49 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Richard Bos 2005-04-28 20:51:56 UTC
Version:           3.4 (using KDE KDE 3.4.0)
Installed from:    SuSE RPMs
OS:                Linux

If one schedules an event from 1800 hours on e.g. Tuesday and
the event finishes the next day (Wednesday) at 0300 hours, the
that is normally displayed in front of the event in the
month view is not displayed.. :(

The raw data for this looks like:
DTSTART;VALUE=DATE:20050425T220000
DTEND;VALUE=DATE:20050426T030000

Changing the DTEND to e.g. 20050424T234500 shows the time
in the month view again.
Comment 1 Bram Schoenmakers 2005-06-01 16:22:39 UTC
Are you sure about the date of your modified DTEND? I assume you mean
DTEND;VALUE=DATE:20050426T234500.
Comment 2 Richard Bos 2005-06-01 17:50:57 UTC
This time the times have been copied from the ical file:

DTSTART;VALUE=DATE:20050511T220000
DTEND;VALUE=DATE:20050511T234500

DTEND used to be:
DTEND;VALUE=DATE:20050512T030000

The difference is that with the DTSTART and DTEND on the same date the time
information is shown in the monthly view. If DTSTART and DTEND are on a 
different date the time is not shown.

In the multidate case the monthly view shows 
(-- entry entry --) 
and in the single date case it shows:
22:00 entry
Comment 3 Reinhold Kainhofer 2006-11-02 19:09:46 UTC
Reassigning all KOrganizer bug reports and wishes to the newly created 
korganizer-devel mailing list.
Comment 4 Sergio Martins 2009-01-07 05:37:16 UTC
Unreproducible in trunk
Comment 5 Richard Bos 2009-01-07 13:49:01 UTC
Problem seems to be gone indeed (tested with 4.1.87)