Version: 3.5.5 (using KDE 3.5.5 "release 19.1" , openSUSE ) Compiler: Target: i586-suse-linux OS: Linux (i686) release 2.6.13-15.12-default Following example: I have a current appointment starting on some weekday, let's say Monday, which occures every four weeks (meaning next occurence is Monday four weeks in the future, and again four weeks in the future (Monday), and so on).. Considering a movement of the initial or any other appointment in this set to some other weekday let's say Wednesday of the same week leaves the follow-up appointments on it's initial weekday (in this example Monday). When specifying a reoccuring appointment in a manner of week-spans this behaviour doesn't make sense, because you want to have a four week span between appointments, which you don't have if you move some appointment to any other weekday in the current week of the appointment your are moving. (Note moving an appointment to some other weekday of a coming week works perfectly, week-span and day-movement are preserved). So it should be like this if you move such an appointment like in the example above from Monday to Wednesday in the same week the appointment already is in, all future appointments should also be updated to the new weekday.
!!ups... seems like the problem with updating follow-up occurences exists anyway even when moving an appointment to some other weekday in an other week than the current!!
Am Montag, 18. Dezember 2006 14:18 schrieb Martin Neuwirth: > I have a current appointment starting on some weekday, let's say Monday, > which occures every four weeks [...] > So it should be like this if you move such an appointment like in the > example above from Monday to Wednesday in the same week the appointment > already is in, all future appointments should also be updated to the new > weekday. Well, it soulds so easy in this case. However, there are other cases, where it is no so easy. - -) You have an event that occurs every other monday and wednesday. If you move the monday event to tuesday, how should the recurrence be updated? To tuesday and wednesday? Or should both be moved, so the event appears every second tuesday and thursday. - -) If you have an event that occurs every two weeks on monday and wednesday, and you move the monday event to the week before, what shall be the resulting recurrence? - -) If you have a montly recurrence, e.g. on the last day of the month, and you move it to next, should it be changed to recur on every first of the month? - -) If you have a monthly recurrence on the 25 of each month and you move it to a 31st, that event won't occur in months with only 30 days... Will the user be aware of this? - -) If you have a monthly recurrence on the first tuesday of each month and you move it one day earlier (to the first monday), you would expect that all following events are also moved one day earlier, right? But that's not the case because in months where the first day is a tuesday, the first monday is six days later and not one day earlier... So, in short, I have thought about modifying recurrence rules on moving events quite a lot, but there are so many pitfalls, that I have not yet found a good way to adapt the recurrence rule in a way that achieves what most users would probably expect. So I simply decided to not touch the recurrence rule at all. Cheers, Reinhold
Am Montag, 18. Dezember 2006 14:45 schrieb Reinhold Kainhofer: > - -) You have an event that occurs every other monday and wednesday. If you > move the monday event to tuesday, how should the recurrence be updated? To > tuesday and wednesday? Or should both be moved, so the event appears every > second tuesday and thursday. I would say only the best is to only update what the user moves. In this case it would result in tuesday+wednesday, because the user is only moving the tuesday event. if he would have liked to change it to tuesday+thursday, he would have to move the wednesday event to thursday as well. > > - -) If you have an event that occurs every two weeks on monday and > wednesday, and you move the monday event to the week before, what shall be > the resulting recurrence? again only modifying/updating what the user moves. in this case if he moves the monday to some day in the week before let's say wednesday to keep it complicated :) (because there already is a wednesday event).. the result should be an appointment each week on wednesday, but it's still two separate events only with a span of two weeks. In order to help the user becoming aware of this, there should be appropriate messages displayed to the user what he is doing. > > - -) If you have a montly recurrence, e.g. on the last day of the month, > and you move it to next, should it be changed to recur on every first of > the month? Yupp exactly, because this is what the user is doing.. moving events and dropping them. Then the schedule should be updated according to whatever occurence is specified within the event. This introduces something new.. consider a movement from the last of a month to somewhere in the middle of a month, then the event should be updated to occure just on that particular day each month, because "last of a month" doesn't say anything else than a particular day of a month. Although the user has to be informed that there could be a problem with the month february because it has less days, but I guess that this problem exists anyway when defining an event which occures on a particular day each month. Haven't looked at that yet how it's currently handled. > > - -) If you have a monthly recurrence on the 25 of each month and you move > it to a 31st, that event won't occur in months with only 30 days... Will > the user be aware of this? if you move it to the 31st of a month, the program should assume that the event is ment to occure on a particular day of a month (before it was the 25th and now it should be changed to the "last of a month".. the user should be informed about that in an appropriate message). but this problem doesn't only exist with the 30th and 31st.. february is a special month in that case. So if you drag an event to the 31st (last day) of a month or the 30th (last day) of a month the event should occure on the last day in february. if you move it to the last day in february it should occure either on the 30th or 31st meaning last day of other months. > > - -) If you have a monthly recurrence on the first tuesday of each month > and you move it one day earlier (to the first monday), you would expect > that all following events are also moved one day earlier, right? > But that's not the case because in months where the first day is a tuesday, > the first monday is six days later and not one day earlier... Yes, I would expect that, because the user should know what he/she wants. Moving some event which is predefined to occure on as you say the first tuesday of a month, and the user moves it within a month in which there also is a monday before the first tuesday, the program has to believe that the user wants to change this event which occured every first tuesday to every first monday, even if this means that next month the first monday will be a little bit later... My point of view is understanding the user's actions and reacting to them. The programs point of view should be to assume that the user knows what (s)he is doing and to aid the user in terms of automatically updating events for him/her (inform about updates). This is the main advantage of a computer driven calendar compared to a paper based calendar.
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of korganizer (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.