Closed (fixed)
Project:
GMap Module
Version:
5.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Reporter:
Created:
19 Jun 2008 at 17:06 UTC
Updated:
31 Jul 2008 at 04:47 UTC
Jump to comment: Most recent file
After a bit investigation it looks like obj.map.setCenter is being called after each marker is added. It should only be called once, after all of the markers have been added. This workaround works for me but I'm not totally sure about the logic/placement.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | marker-event-speedup.patch | 2.08 KB | bdragon |
| gmap-5.x-1.x-dev.patch | 1.25 KB | jsenich |
Comments
Comment #1
bdragon commentedOoh, that gave me a great idea... I can put it in the markersready event!
Committed. http://drupal.org/cvs?commit=123684
Comment #2
marcoBauli commentedthis still to happens on maps with more than a hundred of markers. Also the browser (IE, FF, Safari) throws the error:
"A script in this page has stopped working. You can stop the script now, or wait"
Comment #3
bdragon commentedDo you get that for this?:
http://gmap.chicagotech.org/node/5
Comment #4
marcoBauli commentedumm, nope, the map on your URL loads fine and quick actually..
Updated to beta1: now the error is gone, but loading the map on IE and FF takes literally ages..
i just sent you a web address where you can see this.
PS: the map is generated with gmap_views + cck content-type + location api.
thx
Comment #5
bdragon commentedHmm, I'm going to guess mass attaching of event handlers...
I have considered using a map level event handler instead of individual handlers... I should implement that and see if it helps...
Comment #6
bdragon commentedHere's an alternate way of binding the events that should theoretically help a lot.
How much does this improve things?
Comment #7
bdragon commentedComment #8
marcoBauli commentedbdragon,
the issue seems fixed after an upgrade to beta2. Now map and markers (350 circa) load in a snap!
tryed your last patch to see if this could be pushed even faster, but did not notice any improvement.
thanks for your effort on this delicious module ;)
Comment #9
bdragon commentedComment #10
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.