First of all, I'm new to Directory Opus and checking out its features. It looks fantastic, and will allow me to live with Windows 10. Good job.
My question: if a 32-bit process running under 64-bit Windows launches an explorer window, I'm guessing that the (64-bit) Directory Opus process won't be able to intercept that call, correct? (Unless it uses a separate 32-bit process to do so).
I ask because I have an old 32-bit program that opens folders, and it still opens Windows Explorer.
It works fine. On 64-bit Windows we install both 32-bit and 64-bit components where needed to make things like Explorer Replacement work in both 32-bit and 64-bit processes.
Ahh, clever! Then I suppose it's just the way the program is calling Explorer that prevents it being intercepted.
The ancient program in question is WinGo. I've found an alternative called QuickAccessPopup that works fine (in fact it recognises DirectoryOpus during setup). I'm sure there are others.
If something explicitly runs explorer.exe and/or uses ShellExecuteEx with the "open" verb (instead of leaving the verb null and picking up the default verb), then we don't usually intercept those instances, by design, since there are times when you need to run Explorer itself and intercepting those would cause problems.
Everything else should be covered, though. The usual cases are using ShellExecuteEx with a null verb (which is like double-clicking a folder), or using the more advanced SHOpenFolderAndSelectItems API, both of which Opus will handle.