Hi,
Thanks for the reply.
Is this the kinda thing you are talking about?
jQuery.post("/test.cgi", {
ajax_do: 'wiki_ajax_map_google',
southWest: southWest,
northEast: northEast,
level: map.getZoom(),
current_article_id: 18,
success: function(){
alert("at success");
}
});
..instead of:
jQuery.post("/test.cgi", {
ajax_do: 'wiki_ajax_map_google',
southWest: southWest,
northEast: northEast,
level: map.getZoom(),
current_article_id: 18
}, function(response) {
alerrt("doing stuff");
});
Cheers
Andy
On Mar 17, 8:24 pm, Rossko <[email protected]> wrote:
> > As a random idea, I got rid of the onload= bit, and changed to:
>
> Yup, its a random idea. Random changes are really unlikely to fix
> your issue, compared to understanding what is happening. Put all your
> load and onload stuff back as it was, it was fine.
>
> Go back tohttp://econym.org.uk/gmap/async.htm
>
> Code A
> Async_function ( some params , callbackfunc)
> Code B
>
> Order of events:
> Code A runs
> Async_function is triggered
> Code B runs
> A hundred years later, in browser terms, some data returns that
> Async_function asked for, and *at that time* callbackfunc is run.
>
> The data is *never* available to code B. If you want to do something
> with the data, you have to do it inside callbackfunc.
>
> http://www.google.com/search?q=how+to+use+jquery.post
--
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.
