Hi,
since the request is async, that implies that the classic way of
programming where everything is sequential doesn't work :
Exemple : if you do your geocode request on line '1' - stepping to
line '2' doesn't mean that you have received the answer from the
geocoder yet
That's why you have a callback function : "function(results,status)
{ };" which can be called at anytime, when your answer has been
camputed by google
So you can imbricate the second geocoder call in the first callback
function
or trig an event yourself after each receive to start the next
geocoder call
On Jul 20, 2:21 pm, Nico <[email protected]> wrote:
> Ok .. I tried a few things and it seems that I don't quite understand
> the context of asynchronous here...
>
> I noticed that the reversegeocoding only works when I insert the index
> of my for-loop into alert. So I thought that I basically have to spend
> as much time as getting the index and made some kind of wait-function
> and delayed the program for up to 1 second and at the same point as
> the alert-function, but it didn't work. You might call this attempt
> stupid, but I don't know what else to do.
>
> I'm really trying hard to understand what's going on and how to find
> some kind of solution, but I just can't do it on my own.
--
You received this message because you are subscribed to the Google Groups
"Google Maps JavaScript API v3" 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-js-api-v3?hl=en.
