@Perry Mowbray: More feedback on the FARR TimeZone plugin.
1. Why it crashed on update: (as per post above)
I had put the TimeZone plugin into a folder called
"FARRTimeZone".
When you got DcUpdater to install/update the TimeZone plugin, you had it set so that it put it into a folder called
"TimeZone".
I think that got FARR trying to update and run 2 instances of the TimeZone plugin. Result = FARR crashed and when I restarted it, TimeZone was all "wrong" (it had lost my settings).
My fix for this:
(a) Delete the folder called
"TimeZone" (which contained the TimeZone default settings from DcUpdater's latest update).
(b) Rename folder
"FARRTimeZone" to
"TimeZone" (this folder contained my personal TimeZone settings).
(c) Restart DcUpdater, which installed the TimeZone update into the "TimeZone" folder and preserved my settings.
Here is a picture of the folders in my FARR Plugins directory after this:
2. You've done a better job than Google! Today, I was playing about with the Google-developed Google Desktop clock gadget called
"Time Around the World" (which looked quite nice).
Guess what? It gets the time wrong (and it's not easily fixable by the user).
I would hazard a guess that at least one problem with that is in it not being able to account for "local time" for me being New Zealand Summer Time (1 hour difference).
Kudos to Perry Mowbray.