As Ross said there was a bug causing the problem. The bug was fixed for version 2.137.
On 12 nov, 16:41, estatio <[EMAIL PROTECTED]> wrote: > Ross, Thank you very much for your answer. > > I will get a debugger to see the possible errors that my code has. > > I'm also thinking that it is a bug in v2, I mean the code is so simple > and it's crashing for no reason!!, so if somebody has experience with > this please put your comments. > > I need to show diffenent color bars for different variables, so I > don't know if that is the best way to do it, but I'll think about > it. > > Thanks again Ross, I'll let you know if I'm able to solve the > problem. > > On 12 nov, 14:28, Rossko <[EMAIL PROTECTED]> wrote: > > > > I think the problem is not declaring globally 'map' and 'bar' because > > > as it says on the link that you gave me: "If you assign a value to a > > > variable without first "var"ing it, then a global variable of that > > > name is created for you." > > > That isn't quite true in all browsers .. if you have a DOM object > > called 'map', like for instance a <div id='map' ... then you won't get > > what you expect at all. Never let javascript guess what you're > > trying to do, be explicit and make it do exactly what you want. > > > > However, I declared both variables and it is still not working. > > > You need to get a debugger so that you get meaningful error messages. > > The IE error reports are useless as far as line numbers go, but it is > > also telling you > > 'Error : offsetwidth is null ...' > > > The error I saw before was 'bar has no properties.. ' or something > > similar. > > > So, now it's crashing quite differently in the maps API - although it > > looks the same on the screen, because its still crashing in your toggle > > () function. > > > Something's going wrong with sizing or positioning the GScreenOverlay > > but I don't know what. I think it works first time because the image > > has to be fetched; second time it is in cache and some timing will be > > different. > > > It's beginning to look like a bug in v=2 (now that you've fixed your > > example page) but perhaps someone cleverer than me can take a > > look ...?? > > > You may be able to circumvent the problem altogether by creating your > > GScreenOverlay just once when you initialise the map, and using .hide > > () and .show() to switch visibility. > > > 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 -~----------~----~----~----~------~----~------~--~---
