release 1.19

» Back to forum topics
  1 post   Feedicon  
Replies: 0 - Last Post: November 17, 2009 10:15
by: kmorris
« Older Topic » Newer Topic
showing 1 - 1 of 1
 
kmorris
Defaultpersonimage
Posted: November 17, 2009 10:15 by kmorris
» Permalink
This release is a quick improvement to the timezone validation. There are now two conditions it identifies. If either of these are detected (when timezone validation is turned on), a dialog box prompts the user to continue or stop the upload:

  • The timezone mapping in Preferences maps an iCal timezone to a timezone that is not understood by the calendar server.
  • A timezone used in one of the calendars being copied does not map to a timezone understood by the server, and the timezone mapping in jCalendarCopy's Preferences does not map it to an alternative that is understood.

In both cases, the correct response is to use Preferences to map the timezone to a valid Sun Java Calendar Server timezone.

I removed a validation check that reported iCal timezones that are mapped in Preferences but not used in any actual calendar, since it does not result in loss of data.

There is no affect unless timezone validation is turned on in Preferences.
Replies: 0 - Last Post: November 17, 2009 10:15
by: kmorris
« Older Topic » Newer Topic
  • Mysql
  • Glassfish
  • Jruby
  • Rails
  • Nblogo
Terms of Use; Privacy Policy;
© 2010, Oracle Corporation and/or its affiliates
(revision 20120518.3c65429)
 
 
Close
loading
Please Confirm
Close