No thanks on the scripts side of things, and don’t worry about putting my name on things – all this is out for the world to take and play with as they please.

Only thing I added was an clearOverlay() function to delete all the markers from the map on every ‘idle’ event, right before new markers are added to the map. I’m not 100% sure it’s really necessary, though. In any case, it seems the ‘idle’ event, as well as the ‘bounds_changed’ event, are firing way too quickly (because of tile loading) and sometimes markers are “doubled” on the map. Can’t do much about that, it seems…

I have the brand new implementation at http://cud.dvartora.ro/inprogress, and I’ll keep it there for a few hours (then I’ll put the working script in the root folder and continue working, cause I have some other stuff to do for this website). If you want to copy and scripts, you can do that. Or if you want me to email them to you, just let me know.

Many many thanks again. You’ve saved my sanity today… Take care.

I click one or two and the windows open and closed as expected…on some of them. But others not.

Are you somehow adding the points more than once?

Well I have your code, and data, I might try something tonight as you now have my attention.

In any case, I will try to start again from scratch, following your 6 steps. Hopefully, I will be successful. If not, I’ll bother you again.

Many thanks again,
Sorin

Here are the steps:

1. Create your map
2. Get your data for your markers
3. For each bit of data, create a marker, add it to your map
4. For each marker add the click event
5. Create a global info window variable
6. When the click happens, set the content in the infowindow, and then call the open method with the map and the marker.

That’s it. Stray from that, and you will get into bother.

What you seem to be doing is creating a bunch of markers, and then an infowindow for EACH marker and storing the infowindow in an array. You then open the associated infowindow when you click a marker. Thus the previous infowindow stays open as it doesn’t know (or really care) another info window has opened.

If you use 1 info window only, it will react properly when you call the open method again with a different marker.

So follow the steps above, and see. Any bother you can hire me to rewrite your code (am cheap, a pint and bit of dinner generally enough).

for (var i=0; i < markers.length; i++) {
infowindows[i].close();
} // end for loop
infowindows.clear();

so it should work, no? Only then I do:
infowindows.push(infoWindow);

Also, in the other implementation, based on your solution (http://cud.dvartora.ro/youarenotme), where only one infowindow should be opened and "moved" from marker to marker, there are ALSO multiple infowindows open at one time. Also, there, the script generates multiple markers too, at the same location.

I'm really baffled with both implementations, each in its own way…

var infoWindow = new google.maps.InfoWindow({
content: infoWindowContent[number]
});
/* other code */
infowindows.clear();
infowindows.push(infoWindow);

Then you are essentially adding a new info window each time. You will notice my code uses only 1 info window, and applies the marker to it, when the marker is clicked:

for (var i = 0; i < markers.length; i++) {
var marker = markers[i];

// I really should move this outside the loop as it would be cleaner, but i got lazy!
var infowindow = new google.maps.InfoWindow({
content: “holding…”
});

google.maps.event.addListener(marker, ‘click’, function () {
// where I have added .html to the marker object.
infowindow.setContent(this.html);
infowindow.open(map, this);
});
}

The Google api then closes the current info window, applies the html, and reopens it at the new marker point.

So that’s possibly why the info windows don’t close, you are creating a new one each time, and a close event isn’t sent to the other infowindows.

Now, I am working on an implementation at http://cud.dvartora.ro and can’t seem to make it work as it should. The script is at http://cud.dvartora.ro/gmap.js . Basically, I am loading the markers from a mySQL database dynamically via XML (depending on the area of the map being shown). If the map bounds change, the script is supposed to clear the markers and load the new markers for that particular area from the database. So, the sites array needs to be dynamically generated each time the bounds of the viewport change.

For some reason, the clearing of previous markers doesn’t work properly. I get multiple markers at the same (or almost the same) location, as shown by the fact that the shadow seems to darken, and gets bigger. Just enter “Bucharest, Romania” in the search field, click “Cautare” (Search), zoom out a few times and you’ll see what I mean.

Also, in your example, the infoWindow “moved” when you clicked on another marker. In my implementation, a new infoWindow is open and the ones that are already open for other markers stay open, which is not what I want.

I am sure I am missing something. Any and all help will be greatly appreciated, as I have done all I know and I’ve been pulling my hair with this for 3 days in a row already…

Many thanks.

http://ratemyyogateacher.co.uk/map.html

Let me know how you get on with that,

Colin