🚀 go-pugleaf

Remy,

> You need to call Application->ProcessMessages() periodically in your
> loop.  Maybe also Sleep() as well.

I tried this before posting and it didn't seem to have much of an effect. I
moved the code from my test app into the actual program and it doesn't
seem to lock up nearly as bad.

> Also, your loop is checking for a blank "display" property, which may
> not always be blank, even when the div disappears.  It might be
> getting set to "none" instead of "".

Correct, as soon as it's done loading display goes to none. That's why
I loop until it's set with something.

> Amsuming the page is using an XMLHttpRequest object, you could try
> hooking its onreadystatechange event, and then query its readystate
> property when it changes to see when the tansmission is finished (or
> just query the readystate in a loop instead of using an event).  You
> can also retrieve the data of the response, if needed.

Ah great, that's what I was hoping for. I'll give that a shot.


> The OnDocumentComplete event is the most ideal place for that logic.

Correct, though the web page only gets loaded once, and then everything
else is updated via AJAX.

> Of course.  Because you are not allowing any new messages to be
> processed.

True, but as I pointed out I did try to use
Application->ProcessMessages() without having much improvement.
I think the event you mentioned  above will work fine.

Thanks!

-Tom