The batch-scan option makes a bit more sense in the context of the xscanimage GUI. I'm not sure it's a bug with the HPLIP package so much as a design choice.
It seems there are two options that would make gscan2pdf work fine with this printer:
1) Implement some logic like this, since it's implied you want to use the ADF if you're scanning more than one page at a time:
if (pages == 'all' || pages > 1) {
if (batch-scan-option-present) {
enable batch-scan
}
}
2) Detect when the ADF is out of paper and stop scanning then. The xcanimage GUI shows a message "Failed to start scanner: Document feeder out of documents" when there's nothing in the flatbed, so I imagine that type of detection is possible.
The batch-scan option makes a bit more sense in the context of the xscanimage GUI. I'm not sure it's a bug with the HPLIP package so much as a design choice.
It seems there are two options that would make gscan2pdf work fine with this printer:
1) Implement some logic like this, since it's implied you want to use the ADF if you're scanning more than one page at a time: scan-option- present) {
if (pages == 'all' || pages > 1) {
if (batch-
enable batch-scan
}
}
2) Detect when the ADF is out of paper and stop scanning then. The xcanimage GUI shows a message "Failed to start scanner: Document feeder out of documents" when there's nothing in the flatbed, so I imagine that type of detection is possible.