FFS won't exit

[giaglis]

Hi!
I'm using version 5.22 on Windows 7 Ultimate. I've set up an FFS batch job so that on completion it will run another executable.
The comparison procedure finishes, the executable is run, but FFS won't exit. It remains non-responsive, waiting for the executable to finish (and then it exits, too).

The same version, the same batch job on another computer running Win 7 Home has no problem.

I'm "sensing" it might be a Windows problem, but I had nowhere else to turn to :)

And another opportunity to say: Thanks Zenju for a great application!

G.

[Zenju]

FFS makes a synchronous call to whatever is entered as "on completion", which means it will wait for the called application to exit. I assume you would want an asynchronous call instead? What are you calling?

[giaglis]

First of all, thanks for the reply!

My scenario is simple: I synchronize the database files and then I open the program that works using the database files (it is custom-made, let's call it DBExec). I have created a batch job that does the synchronization and on completion runs DBExec.
So, you're right, I would prefer an asynchronous call. Nevertheless, I don't mind (actually I prefer) watching the progress dialog, clicking on <Close>, and going on with my work with DBExec.

The problem with this particular computer is that after 100% completion of the synchronization, the final progress dialog of FFS goes unresponsive and cannot exit with the <Close> button. (Of course it can be killed using the Task Manager but that's awkward). However, if and when DBExec exits, the FFS final progress dialog regains responsiveness and can be closed normally with the <Close> button.

[Zenju]

The main motivation for the "on completion" was to provide a way to automatically handle system shutdown/sleep and closing the progress dialog. For these tasks it doesn't matter if the command is called async or in sync.
The reason why I chose "sync" as default were scenarios where some command needs to complete before FFS exits, e.g. to avoid conflicts when multiple FFS jobs are scheduled and running right one after another. This however is purely hypothetical. Making an informed judgement on what decision is better would require research on what end users are actually calling - data I unfortunately don't have.
Your scenario seems to suggest async is a better default. Currently I don't see a problem with this settings, so I may very well just change the calling behavior for "on completion".

Here's the new version:
[404, Invalid URL: http://freefilesync.sourceforge.net/FreeFileSync_5.24_beta_Windows_Setup.exe]

[giaglis]

Great, it works just fine!
I hope other users won't be inconvenienced...