Open stevepiercy opened 1 month ago
This could simply be #3. What you can do is disable the "show missed reminders" option in Thunderbird preferences, though I acknowledge that is more a workaround than a fix. Dismissing reminders on someone else's invitation is a bit tricky because it requires modifying your own copy, and that only works on PATCH requests. To implement those I need to fundamentally change how changes are identified and that isn't something I want to do in the current legacy version. I'm rewriting in 224 which has this fixed, but it isn't really usable yet.
I unchecked Show missed reminders for writeable calendars
. I have to wait for another unwriteable event to pass to verify if that workaround avoids the annoyance.
I don't blame you for avoiding legacy code. I often look back at my code, and exclaim, "What was I thinking?"
@kewisch Pardon my ignorance, but what is "224" in reference to? The current version number for Thunderbird and the extension is "128" (more or less), so I doubt that it's a number in that version sequence. I'm curious if the rewritten logic is something that will show up in an update once ready, or if the extension that I have installed is truly legacy and there will be a completely different extension to install at some point? Thank you for all your work!
Sorry, issue 224 on this bugtracker. I didn't want to link it to avoid this issue showing up as a reference. I will push the new code as an update, not a new extension. If you want to try it out you can build the extension from the main
branch of this repository, it has come along pretty far :)
Describe the problem and steps to reproduce it:
Dismiss
for just that event. Nothing happens. See log message below.Dismiss All
. All events that I created are dismissed, but the one to which I was invited persists. See log message below.What happened?
See above.
What did you expect to happen?
When I click
Dismiss
orDismiss All
, the events get dismissed and do not notify me again.Anything else we should know?
I think this issue is different from https://github.com/kewisch/gdata-provider/issues/700.
It was also concluded that this issue was different from https://github.com/kewisch/gdata-provider/issues/498#issuecomment-2227273819 in https://github.com/kewisch/gdata-provider/issues/498#issuecomment-2227426137.
See discussion https://github.com/kewisch/gdata-provider/discussions/708.