Also emit scanProgress(-1) for batch mode scans
Both when doing an automatic batch scan with an ADF and if a batch scan will be triggered by pressing a scanner button, scanProgress(-1)
is emitted, which can be used to indicate that a page has been scanned and a batch process is going on. This is not the case for a timed batch scan, and I think scanProgress(-1)
should also be emitted in this case, shouldn't it?