The calendar team has the bug on it's plate, and they will be working on it as soon as it reaches the top of the stack.

Ordering for the next chunk is never really guaranteed -> it's not like the query creates a snapshot just for you that is guaranteed to be stable.

So the workaround posted here seems to be a fine one (as long as those parameters work :)).

Frank Mantek

On 11/2/06, Tormod < [EMAIL PROTECTED]> wrote:

I think I found a workaround for this:

query.NumberToReceive = 25; // default
query.StartIndex = 0; // default

EventFeed eventFeed = service.Query(query);

while (eventFeed != null && eventFeed.Entries.Count > 0)
{
    foreach (EventEntry entry in eventFeed.Entries)
    {
        // do something
    }
    query.StartIndex += query.NumberToRetrieve;
    eventFeed = service.Query(query);

}

I believe this will read the calendar successively like the
NextChunk-method.



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Google Calendar Data API" 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/google-calendar-help-dataapi
-~----------~----~----~----~------~----~------~--~---

Reply via email to