Quote:
Originally Posted by JKT
Fwiw, my real world experience of this issue occurred over the holiday period where I was away from my desktop for 3 weeks - once I got back, because it hadn't been synched to my Desktop for such a long time, my OmniFocus database on my iDisk had ballooned from a few kb to over 8MB in size and synching took forever. I actually thought it had corrupted so after the first synch, I ended up nuking my database on my iPhone, compacting the desktop database and going through the rigamarole of posting it back to my iDisk and setting up my iPhone again. Of course, it wasn't until afterwards that I read on the forums that this wasn't necessary and the way to 'solve' it was to allow both desk and iPhone to synch and repeat it again within an hour so that the compacting would be performed automatically...
|
Doesn't this show that the Omnifocus "solution" is not really a solution but simply evidence of a flawed model of synchronizing? Another way of viewing this situation is that the choice to keep data all the way back to the oldest sync time is causing this situation. If that were relaxed or changed, the user would not need to be bothered. Omnigroup programmers take note -- a lack of programming foresight on your part should not constitute an emergency on mine. :-)