Closed GoogleCodeExporter closed 9 years ago
Thanks for the report. This is fixed in revision 29de7bc49776.
Original comment by m...@mg.to
on 14 Jul 2011 at 3:31
Original comment by m...@mg.to
on 14 Jul 2011 at 3:33
Is this update reflected in the demo? That still isn't working in Firefox 5
(see attachment, where white circle reflects the location of the mouse). After
you pan the map left, if you roll over the ocean, you will still be getting the
names of states along the eastern seaboard. Also, I'm getting a new error,
"feature.boxes is undefined" on line 428.
Original comment by kat.do...@gmail.com
on 14 Jul 2011 at 9:04
Attachments:
I switched the project from Subversion to Mercurial and forgot to update the
demo page to point to the new code. :-) It should have all the latest fixes now.
I'm not seeing the feature.boxes is undefined error - can you tell me how to
reproduce it? (Or was that on the old demo page? Try it again on the new one.)
Original comment by m...@mg.to
on 14 Jul 2011 at 9:22
Awesome, now it's working perfectly in Firefox. Thanks!
After a little investigating, I figured out that the feature.boxes error was
because I wasn't submitting a bounding box with my geojson, which wasn't
breaking it before. I added that and it worked.
However, I noticed that the rollover seems to be having an issue where it only
works for MultiPolygons. It's not an issue in your demo because they're all
multipolygons, but if you try to use regular 'polygon' and 'multipolygon', only
the multipolygons will show the rollover. Type 'polygon' will give you an error
that says coords[zoom] is undefined @ whatever zoom you're on. I fixed it for
my use by just using all mutipolygons and removing the code in polygonzo.js
that differentiates b/t multi and regular polygons.
Original comment by kat.do...@gmail.com
on 19 Jul 2011 at 11:45
Ah yes, it's using the bbox of each feature now to make the hit testing more
efficient (don't bother checking all the points of a feature if the bbox can
rule it out with a quick test). I could probably make that optional pretty
easily though - but then you'd be back to the slower hit testing.
Thanks for the report on the Polygon bug. I entered that as a separate issue
and fixed it:
http://code.google.com/p/polygonzo/issues/detail?id=13
Original comment by m...@mg.to
on 21 Jul 2011 at 10:10
Original comment by m...@mg.to
on 12 Feb 2013 at 11:46
Original issue reported on code.google.com by
kat.do...@gmail.com
on 5 Jul 2011 at 8:17Attachments: