(In reply to comment #21)
> (In reply to comment #20)
> > Do you think it could be a solution?
>
> As a stupid user, without any knowledge of the programming involved, it seems
> like this is the best solution. As a user, this is the behavior I expect. I'd
> like to be able to go back to finished tasks and put in notes and not have them
> show up in future instances of the task.
It shouldn't be necessary to make multiple tasks out of a single repeating task, each task just needs the ability to:
* store its repeating interval.
* have its interval editable and store the date+time it was edited so that retrospective views of the calendar don't show the task incorrectly occurring at the latest interval. it should allow for multiple edits and the ability to discard invidual or all previous interval settings if the user doesn't care for them.
* have one section of data about the repeated task that is always visible, and again the date+time this data was edited for correct retrospective views
* have date-specific sections of data that are only visible in the calendar on individual dates. this would also mean if the interval was changed, and the old one wasn't kept for retrospective views, then the past information would still be readable in a task history dialogue box and/or by allowing the data to be read in it's nearest past-projected markers in the calendar view (with the actual date preceding the data if different form its past projected date from the new interval)
that probably doesn't read so good but i hope you get my drift.
(In reply to comment #21)
> (In reply to comment #20)
> > Do you think it could be a solution?
>
> As a stupid user, without any knowledge of the programming involved, it seems
> like this is the best solution. As a user, this is the behavior I expect. I'd
> like to be able to go back to finished tasks and put in notes and not have them
> show up in future instances of the task.
It shouldn't be necessary to make multiple tasks out of a single repeating task, each task just needs the ability to:
* store its repeating interval.
* have its interval editable and store the date+time it was edited so that retrospective views of the calendar don't show the task incorrectly occurring at the latest interval. it should allow for multiple edits and the ability to discard invidual or all previous interval settings if the user doesn't care for them.
* have one section of data about the repeated task that is always visible, and again the date+time this data was edited for correct retrospective views
* have date-specific sections of data that are only visible in the calendar on individual dates. this would also mean if the interval was changed, and the old one wasn't kept for retrospective views, then the past information would still be readable in a task history dialogue box and/or by allowing the data to be read in it's nearest past-projected markers in the calendar view (with the actual date preceding the data if different form its past projected date from the new interval)
that probably doesn't read so good but i hope you get my drift.