[11.50b2] An outgoing call cannot be made since the application is dispatching an input-synchronous call

[andry81]

I don't know is that a bug or intended behavior.

Repro:

1. start moving a local directory to the network drive
2. move the moving process dialog to the background
3. the moving process suspended on the deletion something in the local drive counterpart (readonly maybe files)
4. go to a local directory or another local drive and try to open Windows Explorer window using TC context menu: Right mouse button in `[..]` and click on first item.

The modal dialog with the title shows.

[ghisler(Author)]

This is due to a Windows restriction, which cannot be avoided. Here is a description of what is happening:
https://stackoverflow.com/questions/8839195/an-outgoing-call-cannot-be-made-since-the-application-is-dispatching-an-input-sy

In short, Windows doesn't allow an OLE/COM call (to launch Explorer) while in a SendMessage call (busy confirmation dialog).

Moderator message from: ghisler(Author) » 2024-12-15, 08:53 UTC

Moved to will not be changed

[andry81]

In short, Windows doesn't allow an OLE/COM call (to launch Explorer) while in a SendMessage call (busy confirmation dialog).

Why not make a call in another thread?

[ghisler(Author)]

I'm already doing that when you double click on a file. But this would be too risky with context menu commands when the context menu itself has to be called from a foreground thread. To many Explorer extensions may misbehave. I'm not willing to take this risk to correct a minor inconvenience, sorry.