🚀 go-pugleaf

"Carlos Moreno" <moreno_h3gd@mochima.com> wrote in message 
news:480d16b3$1@newsgroups.borland.com...

> With TNMHTTP, the above was working flawlessly;  it's on a
> separate thread, so it does not block the GUI.  In particular,
> if I have multiple downloads going on concurrently, I see them
> appear one by one.

That should also be the case with TIdHTTP.  I use TIdHTTP myself in separate 
threads and it works fine for me.

> However, with the Indy HTTP control, it would seem like it
> does block everything

No, it would not.

> I can't even grab the main window and move it; everything freezes
> until *all* downloads are completed and the images do show up
> (all of them simultaneously).

Then you are somehow deadlocking the code that is running in the main 
thread.  That has nothing to do with TIdHTTP itself.

> The HTTP control is running on a separate thread --- how
> come it blocks the entire GUI?

TIdHTTP does not.  None of its operations are running in the main thread, so 
there is nothing to block.  So it has to be your own code that is being 
called by Synchronize() that is doing something it should not be doing, and 
thus blocking the main thread.


Gambit