Wouldn't a better version of the code be
$.blockUI();
searchLocDep( .... );
searchLocArr( .... );
searchLocInt( ... );
setTimeout(function() {
$.unblockUI();
}, 200);
That way all the "search" stuff gets run asap?
On Oct 30, 7:13 pm, Mike Alsup <[EMAIL PROTECTED]> wrote:
> > What was wrong actually ? Why my version with setTimeout didn't work ?
> > Seems pretty basic, block UI, execute some isntructions, unblock.
>
> The point of using setTImeout is the give the browser a chance to
> render the new DOM updates before diving into process-intensive work.
> So you block first, then set a timeout to give the browse a chance to
> catch its breath, then hit it with your other functions.
>
> Mike
