[Kde-pim] Undo and Redo screws up saving of Todo's

[Allen Winter]

On Thursday 13 March 2008 21:15:49 Thomas Thrainer wrote:
> Hello
>
> I'm currently working on the todo view, but i ran into some problems:
>
Yes, and doing a great job too :)

> Undo and redo seem to don't use the "normal" mechanism of notifing views
> about changes. Instead of calling changeIncidenceDisplay() of the view,
> these actions call updateView(). They furthermore change the pointers to
> the todos provided by the calendar instead of the todos poited to by the
> current pointers. Thus, changes are not immediately visible to views as
> they have to update all pointers they hold to todos. Additionally, views
> have possibly a quite big overhead in displaying todos/incidences after un-
> and redos, as they are supposed to update themselfes completely upon
> updateView(). Is this the indented behaviour? Or is this subject of change
> in order to match the "normal" notification mechanism?
>
I don't we have anyone working on KOrganizer who remembers
or can say for sure.  So feel free to make things better as you see fit.

> Furthermore, after performing some Un- or Redos and closing korganizer, the
> todos get screwed up. In particular, the hirarchy of todos gets partly lost
> or is changed.

No idea.

> Is there currently some work in progress concerning un- and redoing? I work
> with current svn (maybe 3 day old build).
>
No, not to my knowledge.

Sorry for my total lack of help on these issues.

-Allen

_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/