Cancelling a transfer causes SFX to lockup

[mikej]

Hi,

With the current release, if I press the Cancel button to stop a transfer in SFX it causes SFX to lock up and I have to close it via Task Manager. This happens for FTP and SFTP connections.

I'm not sure if this is something specific to my setup here.

-Michael

[Maureen]

Thanks for reporting this. There is some additional information that would help us track this down.

- What is your platform (version of Windows and service pack level)?
- Were you doing an upload or download?
- How large was the file being transferred?
- Was it binary or ASCII?
- How did you initiate the transfer (e.g., drag and drop, cut and paste, select menu item, etc.)?

Maureen

[mikej]

Sorry for the delay in replying to this thread, especially as the release version of SFX 3.0 is now available. I have some more details which I think may be useful as this issue still applies in the most recent build of SFX that I've tried.

This happens when dragging a file onto the desktop to download it.. what seems to happen is that when you click cancel there is a slight delay and then a popup message is displayed that reads:

Error Copying File or Folder
Cannot copy file: Cannot read from the source file or disk.

SFX doesn't respond until this is closed, however the message box opens behind the SFX window so I didn't spot it at first.

I tried it with a couple of files e.g. a binary file of about 225K. This is on Win XP SP2.

Let me know if I can provide further details.

Kind regards,

-Michael

[Maureen]

Thanks for the additional information. I am able to reproduce this behavior now. The key was dragging the file to the Windows desktop. We'll look into it and let you know what we find out.

Maureen

[jcj]

mikej -

Thanks for you patience as we've looked into this behaivor.

Unfortunately, although we had a solution that eliminated the Explorer error message, it had a much less desireable side-effect - that of of leaving an incompletely downloaded stub of a file on the Desktop if the drag-and-drop transfer was cancelled. Furthermore, this stub couldn't be accessed or deleted by the user either. So, we backed-out of this change in favor of the annoying but more functional behavior you reported.

We're not done looking at this, however, for the time being, we're going to stick with the existing implementation. If you have any questions or need additional information, please let Maureen or myself know.

Thanks~

~JcJ