Do not start automatic database diagnostics when Batch Processor is running

[bekesizl]

I started a longer export process with the Batch processor.
I left my computer running, but screen locked.
I was wondering, why the export of photos stoppped.
I found, that automatic diagnostics was running and its result window was blocking the batch export process.

I have no problem when diagnostics is run, when computer is idle.
But in my opinion, a running batch export is not equal as having the computer idle.

[Mario]

The diagnosis is support to run only when IMatch is idle, no dialog boxes are open etc.
How did you start the Batch Processor? Was the BP dialog visible when the diagnosis started?

[bekesizl]

Batch processor was processing the files. 
Batch processor was displaying the files processed dialog. 

[Mario]

Ok, I'll have a look.

[bekesizl]

Additional information: the blue notification at the bottom that DB Diagnosis should be done was also visible.

[Mario]

DB Diagnosis should be done was also visible.

This is normal. When IMatch determines that a diagnosis is due, it shows the message, and when IMatch is idle for a while, it starts the diagnosis.

It should of course not run the diagnosis while the BP is running or something else.
I've had a look at the code looks OK (checking if the UI is idle, background processing idle, no dialogs open etc.). Something must not work correctly, I will look into this.

[Mario]

I have fixed this for the next release.