Thanks for that. If you want to be condescending towards me though, please don't do it by proxy.
The reason we can't supply the code is we're a premium user whose software is marketed towards the British National Health Service. The application itself is made up of six projects in various programming languages across multiple servers nationwide and requires specialist training to use and test in any reasonable time-frame. The javascript underlying it is private, for security reasons, and an NDA is not available. We have ascertained by reasonable scientific method (if you'd read) that the issue in question is not caused by the client software's code, which is obviously the most likely cause of any such issue. Since during the development of this application, we've encountered plenty of bugs on both sides of the fence (and in various browsers) we are thus familiar with the process of ascertaining what is causing such issues. The fact that we took an environment which it has been tested against has not been touched in any way, shape or form for the past three months and has been archived in pure binary in a data centre and that 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. Remember "Courtesy never hurts, and sometimes helps" [1] Regards, Danny [1] http://www.catb.org/~esr/faqs/smart-questions.html#id382249 On Dec 15, 1:38 pm, Marcelo <[email protected]> wrote: > Before using the "B.." word, I'd suggest reading > this:http://www.catb.org/%7Eesr/faqs/smart-questions.html#id382249 > > and > this:http://groups.google.com/group/Google-Maps-API/web/suggested-posting-...http://groups.google.com/group/Google-Maps-API/web/why-including-a-li... > > -- > Marcelo -http://maps.forum.nu > -- > > On Dec 15, 2:07 pm, Rushyo <[email protected]> wrote: > > > Hi, > > > A stable build of one of our applications (utilising version 2 stable) > > has encountered some issues from 4-5pm GMT 14th Dec 2009. We confirmed > > this bug was caused by an external influence by rebuilding our > > server's state from a virtual machine snapshot, ruling out development > > changes as a cause of the issue. > > > The issues in question relate to polygons. Specifically the borders of > > those polygons seem to be turning on and off at odd intervals (some > > zooms and not others, even when they are not supposed to exist at all) > > whilst other polygons are not showing at all when they should. > > > Has v2.s been updated and, if so, what changes were made? > > > Regards, > > Danny Moules > > on behalf of iQ Business Ltd -- 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.
