> in earlier times google maps was not able to produce infowindows with > different measures at once. but maybe things are changing ...
"at once" is a different question. You can only have one infowindow open at a time. If you close it, you can re-open a "new" one with with completely different content. > uh, that was one thing i try to avoid. store (obiously) unneeded > information in my database. that would implicate to go through almost > 900 pictures and calculate. Well I'm not sure how you're expecting the browser to guess this either. What I saw on your map was only thumbnails, in either a landscape or portait format. Why not just one-time force the images to fit into a choice of one or the other at fixed sizes? That needn't affect any 'click for larger image' features you may want to add. > now i found out, what opera made so slow. i tried it without loading > the kml files, and operas speed increases. seems, that this browser > can't get along very well with kml rendering issues. it's a pity, > because ie and ff do very well. Each browser has a completely different poly rendering technology, there's nothing you can do about that. I think your slow Opera performance will be down to your many KML files each loading an image tile (not vector poly) from Google. You might be stuck with that if you truly can't combine them so that only one image tile layer would be generated by Google, and you won't render them client-side as polys, but someone more knowledgeable than me might know better. cheers, Ross K --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
