On May 31, 12:30 am, "Pil (Trustworthy from Experience)" <[email protected]> wrote: > On May 31, 2:28 am, pixeled <[email protected]> wrote: > > > well.. i would hope not.. > > It's better to hope that because this bug is already "Accepted" or > "Acknowledged". And it's a regression bug, so it probably will be > fixed soon.
Let me clarify- In the past few decades of coding plug-ins, etc (meaning dealing with the platform os vendor AND a third party entity, such as Google in this case) I tend to operate in the "it must be MY bug- all i have to do is fix MY code, and everything will work- universally. Having now this 'range' /no fly zone where my code works 2 >= vers >= 2.153 and eventually vers > 2.x (when they release the fix) just gives me the heebies.. the "I would hope not" basically meant that something this fundamental (redraw on insertVertex) will have to be tracked, and I will potentially have to keep twiddling the version number in the java after I ship the app.. Yes, using 2.153 works in my example- but I still don't have warm fuzzies, as I can't in my product, truly 'close' this bug- it's something that I'll have to monitor with releases. (2.153 will eventually be phased out, and I'll have to make sure that the next hard coded version I pick doesn't have something else hidden) Everyone here may be accustomed to the more dynamic environment, it was just something that I hadn't anticipated, but I thank everyone who helped out. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
