🚀 go-pugleaf

>> 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.

This sounds reasonable, of course.  The puzzling aspect is that 
it did not behave this way when using TNMHTTP;  the very only 
thing I changed was this (TNMHTTP replaced by TIdHTTP); nothing 
else in the application changed.  (well, several lines changed 
in the code that downloads the content, since the syntax and 
interface for TIdHTTP changes with respect to TNMHTTP --- but 
the changes are absolutely confined to this one file;  nothing 
changed in the rest of the application)

I just tried to see if it could be the file (TFileStream) passed 
to TIdHTTP::Get to indicate where to put the downloaded content 
(which is the one prominent difference w.r.t. TNMHTTP);  I 
added a random component to the file name, in case it could 
be that the same file was downloaded from multiple places 
concurrently.   Did not change the behaviour.

Anyway, will continue to think about this, and look for possible 
suspects!

Thanks,

Carlos
--