Standalone sync: waiting dlg if ext comparer closed quickly

[Flint]

0. Configure CompareTool to some external comparer, and set EditWaitTime to several seconds.
1. Open two similar ZIP archives (so that there was at least one pair of same-named files), open the internal SyncDirs tool, perform the comparison.
2. Launch external comparison of a pair of files, and quickly close the comparer (so that EditWaitTime did not pass).
3. Result is correct: TC detects that focus returned to TC itself, and "understands" that quick closing did not mean an MDI application.
4. Now, do the same with external SyncDirs.
5. Result is incorrect: When the external comparer is opened and closed, TC displays the "Click on Close" dialog.

It seems, that external SyncDirs does not correctly detects focus returning to TC, and thinks that quick closing was caused by running an MDI program.

[ghisler(Author)]

Yes, this is done because many compare tools are indeed MDI programs.

[Flint]

ghisler(Author)
The problem is not that TC can work with MDI comparers. The problem is, that closing a non-MDI comparer is treated like starting an MDI one. Moreover, this is reproduced only with standalone Sync, and not with built-in Sync.