Very nice. I think my only concern would be that the ordering isn't
guaranteed between separate unrelated queries. At least I think I read
that this was the case....
Shak
On 11/2/06, Tormod <[EMAIL PROTECTED]> wrote:
>
> Ok, thanks! I think I found a workaround for the entire problem though:
>
> 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.
>
> On Nov 2, 9:59 am, "Shakil Shaikh" <[EMAIL PROTECTED]> wrote:
> > No, but I was told to submit it as a bug:
> >
> > http://code.google.com/p/google-gdata/issues/detail?id=18&can=2&q=
> >
> > The only critical one it seems.
> >
> > In the meantime, since I'm able to determine the number of returned
> > results by other means, I just set the results per page to a high
> > enough number to get them all. I will change this once NextChunk is
> > fixed.
> >
> > Hope that helps!
> >
> > Shak
> >
> > On 11/2/06, Tormod <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> >
> >
> > > I'm having the same problem. Found a solution yet?
> >
> > > On Oct 13, 7:16 pm, "Shak" <[EMAIL PROTECTED]> wrote:
> > > > Finally:
> >
> > > > I manually entered the magic-cookie private address with start-min and
> > > > start-max parameters into my browser and received XML back with 25
> > > > entries (ie not all of them), and have only two links, of types "feed"
> > > > and "self" respectively. There are no "next" or "post" links.
> >
> > > > It seems that Gcal isn't returning next chunks for some reason.
> >
> > > > Shak
> >
> > > > Shak wrote:
> > > > > Firstly, excuse the mulitple posts. Google Groups doesn't seem to like
> > > > > me, it seems.
> >
> > > > > Secondly, I've done a bit of digging. Although I've not yet seen the
> > > > > XML itself, I do know that my feed is only showing three Links: feed,
> > > > > post, and self. ParseLink doesn't get called more than those three
> > > > > times.
> >
> > > > > Shak
> >
> > > > > Frank Mantek wrote:
> > > > > > I assume you are talking about the .NET code, right? Can you verify
> > > > > > if the
> > > > > > feed you are getting
> > > > > > actually contains a next chunk URI in the XML?
> >
> > > > > > Frank Mantek
> >
> > > > > > On 10/13/06, Shak <[EMAIL PROTECTED]> wrote:
> >
> > > > > > > Whenever I submit an eventquery, the feed's NextChunk property is
> > > > > > > always null. This is the case whether I use my own code or the
> > > > > > > sample
> > > > > > > calendar app.
> >
> > > > > > > If I increase the result page size, then I get more than 25
> > > > > > > results
> > > > > > > back for the same query, so there is definitely more results to
> > > > > > > come.
> > > > > > > I've tried this with various calendar feeds.
> >
> > > > > > > I notice that the sample app doesn't even check for a null
> > > > > > > NextChunk,
> > > > > > > which indicates to me that I should be receiving a value even if
> > > > > > > there
> > > > > > > were no further results. I'm not!
> >
> > > > > > > Has anyone else had this problem? Any ideas on how to fix it? At
> > > > > > > the
> > > > > > > moment, I've forced to ask for 500 or so results at a time.
> >
> > > > > > > Thanks
> >
> > > > > > > Shak
> >
> > > > > > ------=_Part_29833_11123075.1160754498226
> > > > > > Content-Type: text/html; charset=ISO-8859-1
> > > > > > X-Google-AttachSize: 1218
> >
> > > > > > I assume you are talking about the .NET code, right? Can you verify
> > > > > > if the feed you are getting<br>actually contains a next chunk URI
> > > > > > in the XML?<br><br>Frank Mantek<br><br><div><span
> > > > > > class="gmail_quote">On 10/13/06, <b class="gmail_sendername">
> > > > > > Shak</b> <<a href="mailto:[EMAIL PROTECTED]">[EMAIL
> > > > > > PROTECTED]</a>> wrote:</span><blockquote class="gmail_quote"
> > > > > > style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt
> > > > > > 0pt 0.8ex; padding-left: 1ex;"><br>Whenever I submit an eventquery,
> > > > > > the feed's NextChunk property is
> > > > > > <br>always null. This is the case whether I use my own code or the
> > > > > > sample<br>calendar app.<br><br>If I increase the result page size,
> > > > > > then I get more than 25 results<br>back for the same query, so
> > > > > > there is definitely more results to come.
> > > > > > <br>I've tried this with various calendar feeds.<br><br>I notice
> > > > > > that the sample app doesn't even check for a null
> > > > > > NextChunk,<br>which indicates to me that I should be receiving a
> > > > > > value even if there<br>were no further results. I'm not!
> > > > > > <br><br>Has anyone else had this problem? Any ideas on how to fix
> > > > > > it? At the<br>moment, I've forced to ask for 500 or so results at a
> > > > > > time.<br><br>Thanks<br><br>Shak<br><br><br><br><br></blockquote></div><br>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
