v2.10.0

Added

• Unticking a synced calendar asks what should happen to the appointments it already brought in. Until now they simply stayed, and the only way to get rid of them was to delete each one by hand - which is what the reporter, who treats his CalDAV server as the single source of truth, was left doing (#732). The question names the number, so it is not a guess whether three or three hundred are affected, and it offers Keep and Delete rather than Cancel and OK, because both are real choices. Keeping is the default: unticking is often a slip, and it is the only one of the two that can be taken back. The same question now appears when a CalDAV account is disconnected, which used to be the one path that left appointments visible but stripped of the calendar they came from. Deleting is strictly local - it never propagates to the provider, so the calendar stays untouched for everyone else in the household, and switching the calendar back on fetches the appointments again. Appointments you edited yourself are included: "delete all appointments from this calendar" means all of them, and a silent exception would leave rows behind whose origin nobody could tell. Your own local appointments are never touched, not even the ones that use this calendar as their upload target.

Changed

• Connecting a CalDAV account no longer switches on every calendar it finds. An account often carries more than the one calendar you came for - work, birthdays, public holidays - and all of them used to start syncing the moment the connection succeeded, filling the household with appointments nobody asked for and leaving them to be removed one by one. Calendars now arrive unticked, and you pick the ones that should come in. The same applies to a calendar the server reports for the first time on a later refresh. Because an account with nothing ticked would otherwise look broken, the list opens by itself in that state and says so in one line. Ticking a calendar that was already synced keeps working as before, and refreshing still preserves choices you have already made.
• The ICS subscriptions and the calendar picker are one list grammar. They answer the same question - what comes into this household - and looked like two different features doing it: the subscription rows carried no row surface, no minimum height and a different inner spacing than the calendar rows right above them. Both now take the same rule rather than each keeping its own copy of it; the pointer cursor stays with the rows that actually toggle as a whole, since a subscription row is operated by its buttons.