https://bugs.kde.org/show_bug.cgi?id=480426

            Bug ID: 480426
           Summary: Wait for scanner to not be busy before scanning
    Classification: Applications
           Product: Skanlite
           Version: 23.08.4
          Platform: Manjaro
                OS: Linux
            Status: REPORTED
          Severity: wishlist
          Priority: NOR
         Component: general
          Assignee: kare.s...@iki.fi
          Reporter: the.9a3e...@gmail.com
  Target Milestone: ---

SUMMARY
When using the app, particularly when using the Flatbed scanner, I often make a
preview first, select what I want, and then scan. After the preview is done,
the scanner moves the scanner head back to the start. If I press the scan
button before the scanner head has finished moving, Skanlite will complain that
the scanner is busy... While this is correct behaviour and isn't really a bug,
this means that I have to wait for the scanner to finish moving before pressing
the scan button, which is inconvenient. 

Ideally, the app should know that I should start scanning immediately after the
scanner stops being busy. To improve the user experience a little, I would like
to suggest that the app itself wait for the scanner to stop being busy before
starting to scan again, especially if it's right after a preview, with a
timeout of maybe 30-60 seconds.


STEPS TO REPRODUCE
1. Make a preview from the scanner
2. Before the scan head goes back to the starting position, press the scan
button.

OBSERVED RESULT
An error dialog appears with "Scanner is busy"

EXPECTED RESULT
The application waits until the scan head moves back to the start position, and
then starts the scan.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Manjaro Linux
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.113.0
Qt Version: 5.15.12

ADDITIONAL INFORMATION
I am using an HP Officejet Pro 8620 via the network. My laptop is connected
wirelessly to the network, and the printer/scanner is connected via ethernet.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to