502b381975181407f6b1b4ee60a95be139e34784
When a recurrent event is edited, we now are able to only offer the MOD_ALL option when it actually will work. However, we're still left with the problem that we end up applying the instance-specific data onto the main event, through an old hack. The views already aren't able to offer the MOD_ALL property, since they all change the dates of events, but GcalEventEditorDialog can, and it must handle that properly. For now, do the simplest possible approach, which is: retrive the template event and apply all properties that can be applied to it, without letting the start and end days leak into it. We already only allow passing MOD_ALL on situations where the dates aren't really modified, so it should be safe. Fixes https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/882
GNOME Calendar
GNOME Calendar is a simple and beautiful calendar application for GNOME. We give a lot of attention to details, and as such, design is an essential and ongoing effort.
Useful links
- Homepage: https://wiki.gnome.org/Apps/Calendar
- Report issues: https://gitlab.gnome.org/GNOME/gnome-calendar/issues/
- Donate: https://www.gnome.org/friends/
- Translate: https://wiki.gnome.org/TranslationProject
Languages
C
97.6%
Meson
1.2%
CSS
0.7%
Python
0.3%
Shell
0.2%