If I copy file via F5, then TC call FsStatusInfoW with FS_STATUS_OP_GET_MULTI_THREAD from background thread. No any problem here.
ProgressProcW work all ok.
If I try view file via F3, then TC call FsStatusInfoW with FS_STATUS_OP_GET_SINGLE from UI thread. Sometimes it cause deadlock on winsock recv.
In any case ProgressProcW not work. All UI TC not responsible until plugin return from FsGetFileW.
More info here: viewtopic.php?f=6&t=34980&p=356807#p356807
But general question, why not use separated thread for F3? Same like copy file.
Freeze WFX network plugins on view by F3
Moderators: white, Hacker, petermad, Stefan2
- ghisler(Author)
- Site Admin
- Posts: 48083
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
Re: Freeze WFX network plugins on view by F3
You need to call ProgressProc regularly to keep TC active. If you need to call functions which can block for a long time, start a background thread yozurself for the transfer, and just call ProgressProc and sleep in a loop in the foreground thread.
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
Re: Freeze WFX network plugins on view by F3
Thank. I did that. No problem.