XYplorer Beta Club

Follow the steps below to reproduce:
1.ZipPathUnRAR=?:\WinRAR\UnRAR.exe
2.Create an encrypted rar file
3.Select Zip -> Extract Here & Extract to <$folder> & Extract to Other Pane from the right-click menu
4.Leave the password input dialog open. At this point XYplorer will stop responding completely

The dialog is modal but not topmost. You have to close it to continue with the parent window (XYplorer). If anything, this looks more like a WinRAR bug to me.

Tested using Custom File Associations, the dialog box is not modal
"test" *>run """D:\WinRAR\WinRAR.exe"" x -o+ ""<curitem>"" ""E:\Download\""";
After comparison, the command lines are consistent,Does the built-in menu have a special calling method that results in a modal dialog box?

Which menu are you using?

1) Shell context menu | Zip | Extract Here

2) XYplorer native context menu | Zip | Extract Here

3) File | File Special | Extract Here

modal:
XYplorer native context menu | Zip | Extract Here

non-modal:
XYplorer native context menu | Open With | test

Confirmed.

But I don't see why this is a problem.

When extracting large files (>70GB) on slow HDD,You need to wait a long time for the extraction to complete before you can use XYplorer

Only when you ignore the password input. But then you cannot extract.

Does this mean that fixing this issue will result in the inability to extract encrypted files?
Maybe add a submenu dedicated to extracting encrypted files?

Modal dialog seems to be the solution for extracting multiple files?
WinRAR has a "Wait if other WinRAR copies are active" function, but I didn't find the corresponding command line.

What? I don't get it. You said:

4.Leave the password input dialog open.

What do you mean by this?

Okay, I made some tests and I agree. Next version will call it non-modally.

This change seems to have had an effect on SC zip_extract too, recently some of my scripts suddenly started failing, and after troubleshooting, it seems that the script is continuing now, instead of waiting for extraction to complete. I guess I could convert them over to use SC run instead, but before I do that, I thought I would check with you.

Oh yeah. Wait for the next beta. Your scripts will work again without any changes.