On Dec 15, 2:13 pm, Rushyo <[email protected]> wrote: > Thanks for that. If you want to be condescending towards me though, > please don't do it by proxy.
It's not good practice to say there's a bug without providing a demonstrator. > The reason we can't supply the code is we're a premium user whose > software is marketed towards the British National Health Service. Why not ask your Premier rep? That's what you're paying for! > we have poured through our audit log just in case that wasn't strong > enough evidence, leads me to believe it is reasonable to politely > inquire as to whether the version number has, not unreasonably, been > incremented in the meantime. You can check that by outputting G_API_VERSION. However, updates to 2.s are trailed well in advance and the last update to 2.140 was ages ago. A good idea would be to check the issues log, but you don't say whether you're using encoded polylines or not (which is where a link comes in handy: we can see what you're doing). How about http://code.google.com/p/gmaps-api-issues/issues/detail?id=15 ? There is the distinct possibility that any issue is data-related (again, a good reason for a link); a change to the data rather than your code may well change polyline characteristics enough to trigger Issue 15. But you haven't said whether your code rebuild reinstated data from three months ago as well. Andrew -- You received this message because you are subscribed to the Google Groups "Google Maps 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-maps-api?hl=en.
