On Feb 3, 3:16 pm, Andrew Leach <[email protected]> wrote: > On Feb 3, 2:45 pm, bratliff <[email protected]> wrote: > > > > > The other "+E" ought to change the vertical position. > > Yes, but only the horizontal positioning was wrong. The line as I > quoted puts the shape in right place. Perhaps I should have made that > clearer: my comment was about what worked, not how it works! > > I'm just wondering if it's worth testing with Version 2 of the API, to > eliminate or identify Version 3 as the problem with shape attributes. > Unfortunately I can't work out how to change your code to do that. > > Andrew
Thanks very much for your feedback Andrew and others. I cannot waste additional resources (mine or yours) on a total piece of crap browser. I am producing VML elements identical to the API except for insignificant differences in our point reduction algorithms. Theirs works. Mine fails. The same point reduction algorithm works fine in both SVG and CANVAS. I will not change it simply because Microsoft refuses to adhere to industry standards. It is unlikely PolyCluster will ever support VML. If your users use Internet Explorer, I do not recommend the use of PolyCluster. If your users use mobile phones or a decent state of the art browser like Firefox, Opera, Safari or Chrome, PolyCluster is an alternative to the API poly facility offering advantages in both speed and capacity. -- 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.
