Summary: | new event: please keep in sync date&time end and recurrence ending date | ||
---|---|---|---|
Product: | [Applications] korganizer | Reporter: | Maciej Pilichowski <bluedzins> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED INTENTIONAL | ||
Severity: | wishlist | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Maciej Pilichowski
2007-08-14 21:03:30 UTC
Call me numb, but again I don't know exactly what you mean. What exactly do you want to see disabled and why? In general an event has a start and an end, right? With start there is no problem in Korganizer, but with end there is -- because there is no one end, but two ends. So how can you tell which is really valid, or which one is more valid? My wish is that user would see just one end --> if you set event as recurrent "normal" end should be disabled, and this way it would be crystal clear that "recurrent" end is the valid one. However, I don't insist on any particular way of solving it. Am Mittwoch, 15. August 2007 schrieb Maciej Pilichowski:
> In general an event has a start and an end, right? With start there is no
> problem in Korganizer, but with end there is -- because there is no one
> end, but two ends. So how can you tell which is really valid, or which one
> is more valid?
Actually, a recurring event is in fact a sequent of multiple events! In
particular, you have two different events in this case, each with its own
end.
E.g. take an event on Monday, on August 13, from 8:00 to 9:00, recurring
weekly until December 31.
This is entered in korganizer as an event on August 13, 8:00 to 9:00. You then
select weekly recurrence until December 31.
As a result, you have a sequence of events:
-) Aug 13, 8-9 (duration=1 hour)
-) Aug 20, start: 8:00, end: start+duration=9:00
-) Aug 27, start: 8:00, end: start+duration=9:00
...
-) Dec 31, start: 8:00, end: start+duration=9:00
As you can see, the recurrence end date is just the limit up to which date the
sequence of events is generated. The event's end date/time is still
the "real" end time for the event.
Cheers,
Reinhold
And this is a WONTFIX, per Reinholds explaination. Those two end dates are really required. Reinhold thank you for the explanation, could it be put in help (or what's this)? It would really help understand immediately Korganizer concepts without guessing. |