the problem you described may depend on the server you use. We use time range filtering
for server which supports that functionality, otherwise we use completely different
synchronization. If you want a really fast solution please create a demo server/account (+
send me a private email with credentials) and we can check where is the problem.
On 21 Apr 2014, at 21:22, Attila Asztalos <attila.asztalos(a)gmail.com> wrote:
I'm using CalDavZAP 0.10.0.5 and right after
upgrading from an older version I've noticed that an event that is long past due
(last year) but still not completed (still "needing action") is not shown in the
todo list - but after a short while (the first auto-reload I assume - about 2 minutes) it
does show up without any intervention from me. I confirmed the issue by creating a brand
new todo with a future due date (showed up immediately after logging in) which I then
modified to have a due date in the past (started showing up with a delay after login, just
like the other one).