We have several (Australian) users that create meetings in different time zones (e.g. NZ).
Depending on HOW they create those meetings, the Notes client behaves very differently…
If they open their calendar and click the ‘New’ action button to create a meeting, the issue does not appear
If they simply double-click on a time slot, the following issue appears…
A New Zealand meeting is created with a start time (1:00PM) and an end time (2:00PM).
The time zone is then switched from ‘Local’ to ‘GMT+12’ (Auckland), and the Local times are then displayed on the right hand side (11:00AM - 12:00PM).
That all works perfectly.
However, when the ‘Save & Send invitations’ action button is clicked, the meeting times are converted to 3:00PM - 4:00PM (in the NZ time zone) with the local meeting time updated to 1:00PM - 2:00PM.
It seems the time zone switcher may be causing the issue, as I performed a subsequent test…
A New Zealand meeting is created with a start time (1:00PM) and an end time (2:00PM).
The time zone is then switched from ‘Local’ to ‘GMT+12’ (Auckland), and the Local times are then displayed on the right hand side (11:00AM - 12:00PM).
The meeting times are then changed to something else and then RE-SELECTED to make them the original 1:00PM and 2:00PM values
When the ‘Save & Send invitations’ action button is clicked, the meeting times remain exactly as they should be.
Is this the expected behaviour?
Must users select the start/end times AFTER selecting the time zone to ensure the facility works properly?
I have not had any issue with Day Light Saving with Dom. since I was in Sydney for the 2K Olympics, but I wrote a lot of C API code around DST 2001-5 so when I read your issue DST just jumped into my head.
Have I now earned enough Kudos for you to sell me a license for Dom. X so I can test my “dom. extension manager addin” ???