On Jul 4, 9:41 pm, JavaJive <[email protected]> wrote: > Yes. After I finished posting last night, I briefly tried the same > test in Opera v9.64, and was surprised to find that the results were > different! There, GESLimit = 5 worked fine! > > Consequently, having known of Firebug changing behaviour before, I > tried disabling it, using my own Debug.js which simply adds a textarea > to receive console.log messages, but the behaviour in FF3 was just the > same, 2 errors for GESLimit = 5. >
Regarding Firebug, I found there was a problem with timer accuracy on Firefox using window.setTimeout. Also there's a problem with timer resolution on Windows, with around 15 ms between ticks. Taking the parameters of 1024 locations, with additional locations at 128 per second, means the following delay between requests: L = total locations (eg 190x10=1900) N = number of paths (eg 10) var interval = Math.ceil(1000*(S - 1024) / (128*(N-1))); I added 50ms to overcome any rounding issues with the timer resolution. see the following example: http://www.william-map.com/20100703/1/rate.htm ... -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" 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-maps-js-api-v3?hl=en.
