Sorry, I see what you are saying. Let me do some checking. Ray
On Tue, Feb 10, 2009 at 6:51 PM, Ray Baxter <[email protected]> wrote: > As I said, "You''ll have to change the showNav parameter to 1 if you want > your users to be able to navigate backward and forward." > > > Ray > > > On Tue, Feb 10, 2009 at 6:23 PM, Eli <[email protected]> wrote: > >> >> Thanks Ray. The date range query parameter works fine for its own >> purpose, but that's not to designate a start date. You've disabled >> the forward/backward navigation so that you've explicitly limited the >> widget to that range which perfectly exemplifies what I don't want to >> happen. All I want to do is to make sure that the widget starts on a >> particular date, but without any constraints applied to the events >> that appear in the widget. >> >> Eli >> >> On Feb 10, 5:56 pm, Ray Baxter <[email protected]> wrote: >> > Try using the dates parameter with your embedded calendar. >> > There is an example here: >> > >> > Adding Events to Secondary Google Calendars in >> > Python< >> http://67central.com/bc/2008/09/28/adding-events-to-secondary-google-...> >> > >> > Scroll down for the embedded calendar. Its url is: >> > >> > http://www.google.com/calendar/embed?showTitle=0&showNav=0&showDate=0. >> .. >> > >> > You''ll have to change the showNav parameter to 1 if you want your users >> to >> > be able to navigate backward and forward. >> > >> > Ray >> > >> > On Tue, Feb 10, 2009 at 5:26 PM, Eli <[email protected]> wrote: >> > >> > > Googlers, >> > >> > > This subject was addressed in a post title: "specify a start date when >> > > embedding a calendar in a html page" >> > >> > > However, the technique that was suggested which is to use a "dates" >> > > querystring parameter does not appear to be the proper solution to >> > > this inquiry. The reason is because when you specify a date range >> > > only the events that occur within the range are ever visible to your >> > > user. Any events that occur around that range are ignored by the >> > > widget. That is not the desired behavior when trying to designate a >> > > start date. >> > >> > > Are there any other solutions? >> > >> > > Eli >> >> >> > --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
