Bug 134290 - Application lets me quit without saving the todo list (if autosave didn't occurs it's lost)
Summary: Application lets me quit without saving the todo list (if autosave didn't occ...
Status: RESOLVED FIXED
Alias: None
Product: korganizer
Classification: Applications
Component: todoview (show other bugs)
Version: 3.5
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-18 18:57 UTC by Hervé Caulier
Modified: 2009-02-21 23:29 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hervé Caulier 2006-09-18 18:57:23 UTC
Version:           3.5 (using KDE 3.5.2, Kubuntu Package 4:3.5.2-0ubuntu18.1 dapper)
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.15-26-386

If I close Kontact after creating a new "todo", then the application merely closes without saving the todo list.

On quitting, no confirmation box tells that the todo list has been changed but not been saved.

So, as I could not find the save button in menus or among the shortcuts buttons list in order to save manually my todo list before quitting, then what I do is set the auto-save cycle to the shortest term (1 mn) but it's a bit of qmfhqphgqmghq !

Apart from that, I wish you a good day.
Comment 1 Allen Winter 2006-09-18 19:59:54 UTC
Herve,

Was this to-do being saved to a remote resource?  or a local file?
Comment 2 Hervé Caulier 2006-09-18 23:16:21 UTC
Allen,

That to-do was intended to be saved to a local file.

On Monday 18 September 2006 19:59, Allen Winter wrote:
[bugs.kde.org quoted mail]
Comment 3 Reinhold Kainhofer 2006-11-02 19:17:03 UTC
Reassigning all KOrganizer bug reports and wishes to the newly created 
korganizer-devel mailing list.
Comment 4 Sergio Martins 2009-02-21 23:29:24 UTC
deletes are immediately saved, unfortunately there was a bug in CalendarResources::endChanges() that prevented this.

It was fixed in trunk revision 926668.