excellent news! When do you expect 3.0.2?

thanks

Wouter


Op 15 sep 2009, om 08:42 heeft Larry Hendricks het volgende geschreven:

>
> Wouter,
>
> Funny you should suggest that— that's exactly what version 3.0.2 will
> do. It will delay trickle syncing by 10 seconds as well as coalesce
> them. Honestly, I think iCal itself is syncing too fast in Snow
> Leopard. It used to delay at least a few seconds before starting the
> trickle sync.
>
> Thanks
> --
> Larry Hendricks
> [email protected]
> http://spanningsync.com
>
> On Sep 14, 10:35 am, Wouter Vervaat <[email protected]> wrote:
>> Same issue here. SS syncs too fast. Have experienced double entries  
>> as
>> well. Aren't double entries a big no-no for syncing software?
>>
>> Is there a way to let SS wait for 5 or 10 seconds of inactivity after
>> adding/changing/deleting an ical event?
>>
>> I'm using 3.01 on snow leopard 10.6.1
>>
>> thanks
>>
>> Wouter
>>
>> Op 14 sep 2009, om 18:46 heeft fogy het volgende geschreven:
>>
>>
>>
>>> i have a big problem with spanning sync...
>>
>>> first my configuration:
>>
>>> 1. snow leopard
>>> 2. spanning sync newest version
>>> 3. ical
>>> 4. mobile me
>>> 5. iphone
>>
>>> my problem is...
>>
>>> i write a new meeting in my ical
>>
>>> before i'm ready, spanning sync syncs very fast and i get a double
>>> entry or false. so, i must wait a little time and then i edit the
>>> entry and spanning sync syncs...and i get two entries...then i  
>>> wait a
>>> little time and delete the false entry.
>>
>>> it's every day the same problem, every day with every entry... :(
>>
>>> have everyone the same problem?
>>
>>> best,
>>
>>> andy
> >


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Spanning Sync" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/spanningsync?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to