I have two caldav synced servers with multiple calendars each. As the server supplied colors collide, I simply override the colors in the calendar app. That used to work fine
Since upgrading to 4.0.1.45 EA, while I can still change the colors in the app and the changes get properly propagated to other views like the events view, they change back to the server supplied colors after re-syncing or restarting the calendar app. I presume the later triggers a resync, so that may be the same technical issue.
Is that already a known issue? I wouldn’t know where to look for it. But it’s a tad bit annoying
Sorry I didn’t think in advance to the user defined overriding of notebook color when we simplified the code in the QML bindings handling notebook colors with @chris.adams. To rationalize the code there, we defined the color definition in a unique place : the notebook as stored on device by mKCal. Previously, it was also stored in QSettings in addition to the notebook itself. This simplification has the advantage to defined the color in one place only instead of dispersing it into two locations. Sadly, it is impacting the user overridden value since each sync is actually resetting to server value.
Having think about the functionality you want and the fact to have the color in one place only, I arrive to the conclusion that the sync code was to blame. I’m proposing https://git.sailfishos.org/mer-core/buteo-sync-plugin-caldav/merge_requests/77 to fix this. We’re going to discuss with @chris.adams to see if this is a good fix. In short, it will apply the server value only when this value changes. As long as it is untouched server-side, the overridden value on device will be kept.
Just encountered this today after setting up nextcloud. Indeed it happens when you close and open calendar app a gain and it syncs… Really annoying because now my personal calendar color is the same as second calendar color.
