I know that about blockui, but my only reason for going synchronous
would have been so that the calling function would wait until the ajax
call had returned. I didn't need to block the interface. The main
function was generating a display, but needed an array of user ids from
the server. In stead of getting the array first I was trying to call a
function in-line that would get that array and return to be used in the
process of building the display. That would be fine in a synchronous
world. I just had a brain-fart that's all. :o(
Thanks for all the help, everyone. I feel stupid, but at least it's
working now. :o)
Cheers,
Chris
Jörn Zaefferer wrote:
Christopher Jordan schrieb:
Thanks so much for responding. I did manage to work around the
problem, by calling the function with the ajax call first and then the
function that uses the return object second. Both ways work, so it's
nice to see that if I do something like that again, I could just add
an 'async: false' to my ajax call, but I'm guessing that's not the
preferred method.
It should be preferred because synced calls can block the browser for a
long time (in the worst case), something you'd most likely want to avoid.
The blockUI plugin was designed to block user interaction when
necessary, instead of the whole browser.
--
http://cjordan.info
_______________________________________________
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
