Wasn't it pracus who wrote: >So maybe there is some way to render it maunaly? :) >If it is a stupid question then I'm sorry, I'm not a coding guru.
I've not tried it, but the <canvas> documentation says that it uses a non-zero winding number fill rule (whereas the other polygon technologies use an odd-even winding number fill rule). If that is the case for the Chrome implementation of <canvas>, then it should work if you trace the holes in the opposite sense to the outer border. With SVG and VML, if you have two nested paths that are both clockwise, then points in the inner region are wound twice (winding number = 2). Since two is even, it's a hole. If you have two nested paths that are both anticlockwise, then points in the inner region have winding number minus two. Since minus two is even, it's a hole. If you have two nested paths one clockwise and one anticlockwise, then the points in the inner region have winding number zero. Since zero is even, it's a hole. With <canvas>, only the case where the winding number is zero should give a hole. -- http://econym.googlepages.com/index.htm The Blackpool Community Church Javascript Team --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
