VML rendering may fail to draw geometries when coordinate numbers are very high

[ahocevar]

See  http://n2.nabble.com/VectorLayer-disappears-at-zoom-17-(and-lesser).-tt1079719.html

[ahocevar]

The above patch is a first attempt to fix it.

[euzuro]

Hi team. Is this a regression?

If so, please file it under the 2.7 Milestone. If not, let's put it under 2.8 please. Thanks!

[ahocevar]

This is not a regression, but it kind of finishes up the renderer improvements. And because the changes only affect the geometry coordinates in the VML renderer, a visual test on any of the vector examples is enough to ensure that it works and does not cause regressions.

It would, however, be great to get user feedback on that, because I have no test case to see if the patch really fixes the issue.

[ahocevar]

User BrainDrain reports that the patch fixes his issue.

Relevant tests pass in IE6 and IE7. Thanks for any review.

[tschaub]

Looks ok to me. So (with a bit of faith), please commit.

[ahocevar]

(In [8004]) use a local coordinate system starting at (0,0) instead of coordinates just derived from the geometries, resetting it every time the resolution changes. r=tschaub (Pullup #1732)

[euzuro]

(In [8012]) Batch merge for rc2 of 2.7. 'svn merge -r7967:HEAD from trunk (Closes #1733) (Closes #1489) (Closes #1639) (Closes #1718) (Closes #1723) (Closes #1732) (Closes #1616) (Closes #1722)