Quote:
Originally Posted by Ken Case
From the upcoming sneaky peek build's release notes:
OmniFocus will no longer prompt users to synchronize devices which haven't synchronized in over a week. Instead, if the sync database needs to be compacted (i.e. it has over 250 transactions in its sync history) OmniFocus will automatically unregister devices which haven't synchronized in over three weeks.
|
Yikes, please don't make this change, or at least make it possible to disable this behavior. I was glad to find the hidden options in your post #10, and now I'm glad I read ahead. It doesn't matter how I use it--I NEVER want OmniFocus to decide to unregister my device, which might cause me to have to use some workaround just to preserve data.
Here's how I use OmniFocus: I have a copy on my home desktop, which I make changes to about once every 2 weeks. I have a copy on my iPhone, which I make changes to more frequently. But I almost never use my iPhone version at home, as it's easier to just use it on my desktop. And the tasks I enter and modify on my desktop (like paying bills) tend to be different from the ones I enter and modify away from home on my iPhone (like shopping lists).
So I don't care that much if they're out of sync for a while, and I tend to only actually open the iPhone app at home when I'm intending to sync. But I still do want to be able to sync when I want to, and keep one database, not a home one and an on-the-go one.
If the issue you're trying to solve is poor sync performance, perhaps a better solution would be to display a message on the syncing device during a slow sync that says "Your sync is taking a long time because you haven't synced in a while. Sync more often for faster syncs." That would let me decide whether the trouble of syncing more often is worth the benefit of faster syncs, instead of you making a fairly drastic decision for me.
Quote:
Originally Posted by Ken Case
Yes, OmniFocus will automatically drop devices which haven't synchronized in three weeks—but no, that doesn't lose the data on those devices!
|
How can that be? It sounds to me from your description and my usage patterns that my choices would be to either a) let it replace the database on my iPhone, in which case I'd lose local changes, or b) email myself my iPhone database, and somehow figure out what's changed and manually copy things over to my desktop database? Both of those are awful solutions. If they're my only choices, I won't be updating to the version with this change.