Dropping file to the desktop causes desktop to be blocked.

[zxalexis]

Dropping a remote file to a desktop causes desktop icons not to response and "busy cursor" all over the desktop. All other programs and functions of the system are working properly during copying.
It seems that swish blocks out the source and destination folders - why not to copy through temp folder)))

[alamaison]

Replying to zxalexis:

Dropping a remote file to a desktop causes desktop icons not to response and "busy cursor" all over the desktop. All other programs and functions of the system are working properly during copying.

Explorer blocks the folders unless the DropTarget? supports IAsyncOperation. This is planned for the future but won't be easy (will require multiple sessions as libssh2 sessions aren't threadsafe). See ticket #59.

It seems that swish blocks out the source and destination folders - why not to copy through temp folder)))

Copying via a temp folder won't solve it:

• the mechanics of the copy operation aren't the problem. Explorer will always block the target folder unless we support asynchronous operations.
• the temp folder may be on a different disk or even machine to both the source and target requiring a further bocking copy.

[alamaison]

* Ticket #162 marked duplicate of this one *