GNOME Bugzilla – Bug 580724
can't edit recursive events in 2.26
Last modified: 2011-05-27 07:01:16 UTC
using GNOME 2.26.1 * open evolution calendar on monthly view * right click on a day and add an appointment * add a description * select the recursive option, weekly event on the selected day for ever * save the appointment * double click on it * edit recurrency options * change the day * save the event * select to apply to all instance if libical is configure to crash on warning e-d-s will crash, if not the events will not be displayed on the new day in the calendar and in some case only one event will be displayed, restart doesn't makes a difference
Created attachment 134008 [details] [review] Try to get the recurrence objects again if the calendar is busy. This can be completely solved with the eds-dbus port. I have put a work-around solution for this for the moment. I only see the refresh issue, the changes are made properly, but not shown in the monthly. Seb, please apply this patch and let me know if it fixes the issue.
the change doesn't make a difference, change an instance hour and selecting "apply the change to all instances" only update the first one, changing the day doesn't reflect any graphical change on the calendar either
the changes on bug #561312 seems to fix most of the issue, the time are not the same on the calendar view than in the preferences but that might be a different bug
I didn't compile, but looks fine, please commit.
*** Bug 578703 has been marked as a duplicate of this bug. ***
I took the freedom and added a necessary tries++ to increment the counter. I'm all for changing the goto into a for() or while()... e-d-s compiled fine, committed as 692aa504aefdf60f923e253fbd40d32d29a6cb12. Leaving this bug openas the issues haven't been addressed by this patch.
I cann't reproduce the actual problem in Evolution 3.0 Can you please check again whether this issue still happens in Evolution 2.32.2 or Evolution 3.0 and update this report by adding a comment and changing the "Version" field? Thanks a lot.
Please feel free to reopen the bug if the problem still occurs with a newer version of Evolution 3.0.1 or later, thanks.