> problem: content of infowindow slips out of infowindow area, when > first opened under opera browser. i suppose it depends on the included > image, of which i can't pre-estimate the height, because only width is > fixed. second opening is fine, the whole content fits into the > infowindow.
That does make it difficult to offer a fix. If you can't guess the size of your own image, the browser isn't likely to do any better. You could perhaps standardise the size of your thumbnails. You might a choice between two formats, landscape or portrait. > in general, the application under opera is too slow. what can i do > against it ? The introductory page loads a whole load of nearly-identical images to switch between highlighted regions. That doesn't seem very efficient. You could change it load on demand only, or you might change the whole approach - as you're expecting the user to move on to a Google map anyway, why not start with one and educe the overhead of changing pages. GPolygons can be set up to change colour on highlight with reloading images. In your main map page, you could consider - Create your church icon only once, instead of making a new identical copy as each marker is placed. Roll your area KMLs into one, instead of having many KML files each requiring round trips between your host and Google's before ever arriving at the browser. Define your bildf() function in the global namespace, instead of every time you run createMarker() 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 -~----------~----~----~----~------~----~------~--~---
