It's a good workaround until Rainy add an option for time zones.
I have a couple of question about it.
I don't get the idea of to create the event in a calendar and then copy to a temporal one. In this way, you need to create the event, open the manager and move the event to an existing calendar. Or I'm wrong?
Another thought I have is which is the need to use a skin to use something that doesn't need windows? Of course, it has the advantage of an easy installation.
Using only the lua file I copy it in the program/script folder (not the user one). Then, when a event is created in the calendar, it updates the event instead of creating a new one, removing the timezone operator to avoid mistakes. How I avoid the update one and again? creating a new item in the iCal data (X-RAINLENDAR-OFFSETTIME). This solution works only on Rainlendar.
Another possibility is to use this script in all calendars... and remove the exceptions (I didn't do any of those).
But this approach also have errors.
- I don't know how to change the option to show/hide the original time. (except modifying the ini)
- I can't trigger the event handler (redraw). (something related with the new "pending list" warning?). I need to refresh Rainlendar to read it again.
- The ICS shows that the timezone in the location was removed. But Rainlendar still shows it in the event dialog. Somehow it still shows the "previous location" data instead of the event data.