It's a bug. I'll fix it.

Another error (possibly related to the previous one). If I create a Google calendar event in Rainlendar (with a zero minute alarm), then delete it after it's time (by dbl clicking the entry and pressing the 'Delete' button), I get the following error:

"Google Error!
Unable to delete the event.
Server returned result: (0) 409 Conflict."

I can delete the entry ok before it's time though.

I think the conflict happens when the alarm is triggered in Google Calendar it marks it as changed and invalidates all the old versions so it's not possible to make modifications to the event until it has been re-read. If that's the case refreshing Rainlendar should fix the problem.

You're right, refreshing Rainlendar enables me to also delete the Google calendar copy.

It's good to have a workaround but it's inconvenient to have to manually refresh Rainlendar to work as I want - any chance of fixing it so I don't have to refresh it? Preferably transparenty (so it just does it out of my view) or at least by getting Rainlendar to automatically refresh itself when it needs to.

Thanks.

With the default skin, setting the Position to "On Desktop" causes the tooltips to appear underneath the calendar.

andygrunt, It's not possible to get rid of the conflicts completely since it's Google's way to prevent data loss. However in the delete scenario I probably could reload the event if the 409 happens and delete it afterwards. I'd guess that if you are deleting something it probably doesn't matter if the event has been changed in Google calendar. I'll add this to my todo list.