|
|
This hint is guaranteed to cause problems
are you sure that is the case? What happens when you write data to a file and it is saved on the fly, without needing to save on closing? As long as no two people write to the same point in the data file (or perhaps in this case, an appointment time perhaps) the data from both inputs will be saved simultaneously. I'm sure that even the same appointment-simultaneous modification hurdle shouldn't be too tricky to overcome for some wiley developer. In point of fact, ical seems to do on the fly saving right now - enter some data into it, immediately force quit then reopen the app, and your data is right there.
This hint is guaranteed to cause problems
Just because iCal regularly writes changes to the ics files doesn't mean it re-reads them constantly too--it might be working on a copy in memory and just writing out changes--which means the point raised by porkchop_d_clown is still valid.
This hint is guaranteed to cause problems
fair point - but it cannot be out of the realms of possibility to have ical check a calendar more than the one-time-on-opening scenario. As I recall, it does this with subscribed-to calendars in any case (I haven't used one recently so working from foggy memory here) but if ical can manually be asked to check a remote calendar, and update the local contents as a result - through the 'refresh' option - then how tricky can it be to at least fudge the process and make it applescriptable to any refresh speed you choose (or cron-job the action)? Better still of course is to give a possible default refresh option that's quicker than the current fifteen minutes within the app itself.
This hint is guaranteed to cause problems
here's the app; http://ww2.unime.it/flr/isyncal/en/how_sync.html |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.09 seconds |
|