Okay, i've finished rewriting the whole, thing, and to my surprise, I
have exactly the same problem. I'm compiling from RB2005r4 for OSX.
The problem occurs on every platform for any download. The
DownloadComplete event simply isn't firing.
Then, to be absolutely sure, I made it as simple as possible. I made
a window with a pushbutton, a progress bar, and an httpsocket.
Absolutely nothing fancy. And I was surprised again.
Upon clicking my command button, which sets Yield to True and uses
the Get method to download, I got this order of events firing:
1) Connect
2) HeadersReceived
3) ReceiveProgress (repeated until the file is done)
4) PageReceived
Yes, to my surprise, DownloadComplete didn't fire! This raises
another question, how the heck did I manage to get it working in the
first place???
So, is this normal behavior? Should I expect PageReceived to fire
and NOT DownloadComplete? Should I use something other than
HTTPSocket.Get Address to download large files?
Thanks,
Andrew Keller
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
