Version: (using KDE KDE 3.5.5) There is no "Save" button in KOrganizer, so there is no way of forcing it to save calendars. This is very irritating because it is inconsistent with all other apps.
Every change you make is immediately saved. There is no need to save.
1. This is counter-intuitive. 2. Is it saved each time when, for example, file is on remote server using fish? I do not see this happening. 3. Korganizer shows "Modified" in title bar, for example when new event is added.
Iterating through your points: 1) I don't buy that 2) No worries. Calendars on the local harddrive are immediately written to, remote calendars have a buffer and will safe once in a time interval and when you quit KOrganizer 3) Your only statement which makes some sense, perhaps we should remove the [modified] word from the title. Reinhold, Allen, do you agree?
1) It is inconsistent with all other apps. Thus it confuses users. So I think it is usability bug. I know it irritates me, I guess it irritates other people, but it should be up to usability guys to give the decision. 2) So for remote calendars the only choice I have is to wait or close KOrganizer (I am doing the latter BTW). It does not make me comfortable that I am limited only to this choices. It is like you had text editor which saves only every few minutes or on quit. Would you like it? I prefer full control over my apps. 3) The "modified" word disappears after some time, so it suggests even local calendars are not saved immediately.
Am Donnerstag, 19. Oktober 2006 19:10 schrieb Bram Schoenmakers: [bugs.kde.org quoted mail] I agree. There are no calendar apps where your actively have to save the data. You also don't save the data of your mail application or of your file browser. > 2) No worries. Calendars on the local harddrive are immediately written to, > remote calendars have a buffer and will safe once in a time interval and > when you quit KOrganizer Well, for me it seems that even remote calendars are immediately saved (i.e. the delayed saving option doesn't seem to have any effect). > 3) Your only statement which makes some sense, > perhaps we should remove the [modified] word from the title. Exactly. It should only be there if there are really any unsaved changes, i.e. if the current calendar is a CalendarLocal and not a CalendarResources. (We shouldn't distinguish on that, but rather catch the instance when the resource calendar is saved and remove the [modified] propertly). Cheers, Reinhold
For the records, KOrganizer used to provide a save button up to KDE 3.3 (or 3.4?). One could use it to explicitly save the current contents. Note that the calendar was saved automatically on exit nonetheless (and maybe even inbetween).
Reassigning all KOrganizer bug reports and wishes to the newly created korganizer-devel mailing list.
If you want to save explicitly you can right click the resource and choose "Save". Can we close this then?
(In reply to comment #8) > If you want to save explicitly you can right click the resource and choose > "Save". > > Can we close this then? Closing then. Also, this bug doesn't make sense, now that we use akonadi. Please don't reopen it.