I'm using REALbasic 2005r4 on OSX, and the problem occurs on all
platforms using any server and any download. It doesn't matter
whether the application is a debug app or not.
Andrew Keller
On Aug 16, 2006, at 11:30 AM, John Balestrieri wrote:
What platform are you running? Does it happen with files from a
particular server, what about files downloaded from another server?
Does changing the download location change anything, depending on
which server you are downloading from? Maybe it's permissions issue
if you are running on OS X? Debug versus Compiled application? What
if you build for another target, and tested that?
John
On Aug 16, 2006, at 11:20 AM, [EMAIL PROTECTED] wrote:
Okay, more information...
The download does complete successfully. The file is where it is
supposed to be. It's complete and not corrupt. The binary stream
is still open, so quitting the debug application releases the
file, and it's perfectly usable. I'm using HTTPSocket.Get
(Address) to store the file to the hard drive, and I'm using a
thread to monitor progress. When the download has completed, the
ReceiveProgress event fires once more; there is no new data, and
bytesReceived equals totalBytes. Nonetheless, DownloadComplete
does not fire. The socket remains connected and the binary stream
remains open.
And, the question still stands... Is there something simple that
causes the DownloadComplete event to not fire?
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>
