On Dec 3, 6:07 pm, John Mick <[email protected]> wrote: > I'll be leaving for the weekend in a few hours - when I leave today > I'll clear out all my cache and make sure I am loading your SVG > version test and let that run over the weekend, so we'll have several > days of usage to look at on Monday.
Did anything crash ? I added five copies of each poly to the test case. I ran it overnight on a very old computer. It was still running in the morning with no change in speed. I have made several improvements. SVG is the default. I might discard CANVAS. Your application is fairly unique. It helped me isolate & fix some bugs. It is not safe to simply rebuild dirty tiles. It causes the zIndex order to change. Adjacent tiles with different zIndex orders are apparent. If a poly changes position, I have to do a full rebuild. I believe it is working now. Your custom solution will provide the best performance. Both PolyCluster & the API build tiles to expedite dragging, panning & zooming. Since you are doing none, tiles are overkill for you. PolyCluster builds an internal cache to reduce the effort to rebuild tiles previously in view. Again, because you quickly discard your polys, an internal cache is overkill for you. Thanks again for your help. -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" 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-js-api-v3?hl=en.
