[Google Maps API v3] Re: API Documentation

2012-07-10 Thread Enoch Lau (Google Employee)
We use JsDoc Toolkit: http://code.google.com/p/jsdoc-toolkit/ Enoch On Tuesday, July 10, 2012 12:45:14 PM UTC+10, Mihai Danila wrote: Would you happen to know what tool was used to generate the sleek API documentation page for the v3 API? I'd love to use it to document my projects. --

[Google Maps API v3] Re: More information about HeatMapLayer/HeatMapLayerOptions

2012-07-10 Thread Hunter McMillen
I was hoping that you could help me with something else also. When I initially added the HeatmapLayer to our application is was hardcoded but it also worked fine. Now that I have moved it to a proper position in our application I receive this error on the last element of every data array I try

[Google Maps API v3] Re: More information about HeatMapLayer/HeatMapLayerOptions

2012-07-10 Thread Rossko
Any thoughts as to why this could be happening? Wild guesses: You have a superflous comma at the end? Your code attempts to read beyoend the last element? -- You received this message because you are subscribed to the Google Groups Google Maps JavaScript API v3 group. To post to this group,

[Google Maps API v3] Re: More information about HeatMapLayer/HeatMapLayerOptions

2012-07-10 Thread Hunter McMillen
I use a for in loop to iterate over the array so I don't believe that I could be reading past element 334, The extra comma would throw an error in firebug. 327: {location:{$a:-35.5,ab:172},weight:11} object music.js:730 328: {location:{$a:-36.5,ab:151},weight:1} object music.js:730 329:

Re: [Google Maps API v3] Re: More information about HeatMapLayer/HeatMapLayerOptions

2012-07-10 Thread Michael Geary
Clearly, you have an off-by-one error. Or maybe you need a closure. Or something else is wrong. Not much help, is it? :-) Give us a link to a test page and you may get some more useful replies... -Mike On Tue, Jul 10, 2012 at 10:07 AM, Hunter McMillen mcmil...@gmail.comwrote: I use a for in

Re: [Google Maps API v3] Re: More information about HeatMapLayer/HeatMapLayerOptions

2012-07-10 Thread Hunter McMillen
Sorry for the extremely vague description of my problem, I figured out the cause however. The weight property in the WeightedLocation object was being set to a String value when it only accepts numeric values. Sorry for the time waste. Hunter On Tuesday, July 10, 2012 1:49:19 PM UTC-4,