1 week, 5 days ago LynnRHKParticipant
I’ve just downloaded SkedPal and am enjoying it a lot already! I spent the last few days learning about it and decided to give it a go. I have several appointments on my iCloud calendars that are in the “Floating” Time Zone. This means that no matter what time zone I’m in, for example, the appointment always shows up at 3pm. SkedPal is treating those time zones 6 hours earlier. For example, I have a “Floating” appointment for a Weekly Review every Thursday from 10am – 12pm. SkedPal is showing that appointment for 4am – 6am. Can this be fixed? Thanks very much!1 week, 4 days ago SethParticipant
Thanks for bringing this up. Didn’t know about the floating time zone feature of iCloud calendar. We’ll have to learn more about it and improve the integration to support it in the future. The current implementation’s treatment of the floating time zone is probably random.
In the meantime, would it be possible for you to set your current time zone?1 week, 3 days ago LynnRHKParticipant
Thanks so much for the answer. FYI I actually use an app called BusyCal in order to designate the “Floating” Time Zone on ***many*** of my repeating appointments. iCloud/Apple Calendar recognizes and maintains the Floating Time Zone. I am unable, however, to choose/designate the “Floating” Time Zone directly from iCloud/Apple Calendar when I am scheduling appointments.
We are currently dividing our time between two different cities (in different time zones) and I travel back and forth frequently. This Floating Time Zone allows me to keep my Weekly Review, for example, at the same time each week no matter which time zone I happen to be in that week. It basically keeps those appointments as though they were in a paper diary/planner. 10:00am is 10:00am whether I’m in Europe, US, etc.
As a “stop-gap” for now, I can manually change all of those appointments to my current time zone, but this will not work for me long-term. It’s simply too much manual work to change things each time I travel back and forth when a much more elegant and easily implementable solution already exists. Thanks again for being willing to learn about the Floating Time Zone and improve its integration support for SkedPal.
My SkedPal trial ends in 12 days, do you think this improvement might be within that time frame so I can test it before committing to a year’s subscription to SkedPal? Other than this calendar time zone issue, I am enjoying this program and would really like to be able to continue to use and support it! :~)
1 week, 3 days ago SethParticipant
- This reply was modified 1 week, 3 days ago by LynnRHK.
Thanks for sharing this information. It helps us learn and understand your needs. I was thinking an alternative solution is to set and keep your time zone to location A even when you travel to location B. But, I reckon that will create issues when you have to set up meetings with people in location B; right?
We’re currently in full swing with development of SkedPal 3 due to be released by mid-2020. So, we’ll keep this option to be considered for SP 3. I’m afraid we won’t be able to offer a quick solution.5 days, 15 hours ago LynnRHKParticipant
That’s right, keeping time zone set to location A even when I travel to location B would create issues when I have to set up meetings with people in location B.
Please do consider this issue for SP 3. I don’t think it should be a difficult thing to fix? Even BusyCal app itself had implemented the Floating Time Zone incorrectly at one point on the iPhone app. I emailed them and it was fixed a day later! :~)5 days, 14 hours ago LynnRHKParticipant
Just did a bit more research — I didn’t realize that Floating Times aren’t supported by Exchange or Google calendars … Perhaps it can’t work here in SkedPal after all … ?
In case this may be helpful: From the BusyCal website: https://support.busymac.com/help/70609-time-zones#option-3
Option 3: Schedule Events in Floating Time
As an alternative to scheduling events for a specific time zone, you can schedule events in Floating time. An event scheduled at 9:00 AM Floating time, appears at 9:00 AM in all time zones.
This may be useful if you are located in New York (US/Eastern) and are sending a meeting invitation to a client in San Francisco (US/Pacific) for a face-to-face meeting. If you schedule the lunch at noon Eastern and email the invitation to your client in San Francisco, the lunch appointment appears at 9:00 AM on your client’s computer. However, if you schedule the appointment for noon Floating time, the event displays at noon regardless of what time zone you are in. Then, when you travel to San Francisco to meet with your client, you’ll both show up for lunch at noon, regardless of what time zone is set on each computer.
On the other hand, if you’re scheduling a conference call with your client in San Francisco while you are in New York, you should not use Floating time. You’ll want each participant in the conference call to see the event in their local time zone, since a call scheduled for noon Eastern occurs at 9:00 AM Pacific.
Warning: Floating times are not supported by Exchange or Google Calendar. If you are syncing with Exchange or Google Calendar, you should not use Floating time events. Floating times are supported by BusyCal for iOS. And, although the iOS Calendar app doesn’t enable you to create Floating time events, it does let you view and edit such events created in the OS X or iOS version of BusyCal.5 days, 2 hours ago SethParticipant
Thanks for the information. I think it still should be doable in SP 3 because each calendar source (iCloud, Office 365, or Google) will have its own independent integration. In other words, if only the iCloud calendar supports floating time zones, we should be able to set up the integration to support it for iCloud only.
You must be logged in to reply to this topic.