[Korganizer-devel] [Bug 138958] on movement of follow-up appointments (eg. occurence once each month on a specified week day) future appointments don't get moved to the new weekday

[Martin Neuwirth]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=138958         




------- Additional Comments From gfest gmx ch  2006-12-18 16:30 -------
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.