Mark/tag events for deletion, if delete is disabled.

[bbnoc]

Any way to mark an event for deletion, in case deletion is disabled?

That way i can see in outlook, what the others may have removed in google. I do not want to have deletions active, in case something goes wrong.

[phw198]

No, but you can manually delete those items in both calendars...

Not trusting OGCS to not delete, but then trusting it for specific deletes seems a little at odds 😉

[bbnoc]

Maybe I did not explain it precise enough :P

I am loading someone elses google calendar in outlook, and i can add stuff, but it is critical i do not delete the wrong things by mistake.

What i was thinking of, was if someone in the google calendar removes something, it is not deleted in my end because i have deletion deactivated.

If OGCS could tag or mark the event that now does not exist in google, i can manually delete it in my end. It could have a prepended text added to the subject field. Like " DELETED - Remember the dishes"

[phw198]

Ah OK, that does indeed make a little more sense 😉

However, you should be seeing a message "x Outlook items would have been deleted, but you have deletions disabled." and it then proceed to list those items (you need to have "Verbose output" checked). Doesn't that achieve what you need?

[bbnoc]

Yes, sure, i could see it in the softwares log - the idea however was to easily spot in my calendar in outlook on a day to day basis.

I understand this might be a edge case feature, but also probably pretty simple, as there already is functions detecting this, and could qute simply get a line of code extra which prepends a tag, :)

[phw198]

Although using a tag to prefix eg the subject, such fields are used to "reclaim" calendar items by OGCS in certain situations and it would break that mechanism. Similarly, two-way sync would require some care so, unfortunately, I think this is too edge case to include for general availability.

However, it might be possible to cover off your ask using different colours - ie extending #113 and #405 requests. I'll leave this open, but can't make any promises as to when I might get round to this...