Summary: | Wrong day view for events lasting more than 1 month | ||
---|---|---|---|
Product: | [Applications] korganizer | Reporter: | Daniel Olmedilla <olmedilla> |
Component: | otherviews | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | christophe, smartins |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Daniel Olmedilla
2005-07-22 08:19:46 UTC
*** This bug has been marked as a duplicate of 101172 *** Sorry, just realized that this is indeed a different problem. In single-day view, one day is quite a few pixel wide. The event is created over 40 days, which is easily larger than 32000 pixel, which is the max size we use... Thus the cut-off at that point where the threshold is reached. We really need to find a better way to deal with such long events! Reassigning all KOrganizer bug reports and wishes to the newly created korganizer-devel mailing list. > I have currently an event which last for 40 days and has no time
> associated (in fact is just represents that I am not in my office but
> in a visit in a different country). The problem is that all the views
> (week, month, etc...) show the event without any problem except the
> day view. In the day view, I can't see the even in the last 10 days,
> that is, the event is from the 19th sep to 30th oct and if I go to
> the day 25th sep, I can see the event but if I go the 25th oct, then
> the event is not shown.
You are right, that's a problem only in the day view, if one day has quite a
large width. The problem is that we create the widget for the event with its
proper coordinates starting at the correct beginning date (which is not
visible on the left). For very long events, the widget thus exceeds the
maximum widget width...
However, changing this is not so easy, as we need the start date (and in
particular the correct new date) when moving the events...
Cheers,
Reinhold
Cheers,
Reinhold
It works fine in KDE4.2 Confirmed, we cannot reproduce this issue anymore in KDE 4.2. We will close this bug report now. |