yes i do, the key error was from changing from directory nick.deactro
to heymink.nl but didn't change the key that was stupid.
the big deal is the error that i and i gues you also get is:
(a || this.o || this.Ca[0]).getMinimumResolution is not a function
that's in the main.js a file from google that i can't eddit :(

setTimeout was used couse there where no map loaded by the onload
event so i thought maybe it needs a little extra time.
but that also failed :(

i shall post the onload version online :D


On 15 feb, 17:02, Rossko <[email protected]> wrote:
> > created a new key as you said but it diddn't worked out
> > sensor where there btw.
> > copied it from google maps now but it still doesn't work :(
>
> Well you've fixed the key error.  Are you looking at this page
> yourself at all?  You should notice that now we don't get a 'key
> error' prompt, and that mapcontrolsand logo are now appearing.
> You'll also see the browser reporting a javascript error, giving a
> clue as to where the next error is that you need to fix.
>
> Why are you using an unreliable 'setTimeout' to run your maps code,
> why not use the onload event like everybody else?

-- 
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.

Reply via email to