I have added a scan-button to the unix-"select scanner"-dialog.
This still needs to be done for windows. Most of the work is done. What needs to be done:
- add a button to the windows-dialog (extensions/source/scanner/grid.*).
- change extensions/source/scanner/scanwin.cxx so it can handle scanning when the button is pressed.
You can look to the implementation in the unix-classes how it is done there. Please remember that the 2nd parameter of configureScannerAndScan isn't always initialized.
Is this regarding Libreoffice? If so what version are you using? Can you please provide us the steps to duplicate the issue?
We will need to know your OS Version .
A windows specific easy hack I guess; poke at this commit to see things work around there I guess.
Author: Rob Snelders <email@example.com>
Date: Thu Oct 20 21:25:46 2011 +0200
Added a scanbutton to the scan-dialog
Yes Michael that's correct.
I added a scan-button to the scan-settings-dialog in Linux. But I don't have windows so I can't implement it there. This bug describes that one there is also needed.
adding LibreOffice developer list as CC to unresolved EasyHacks for better visibility.
see e.g. http://nabble.documentfoundation.org/minutes-of-ESC-call-td4076214.html for details
Removing comma from whiteboard (please use a space to delimit values in this field)
Migrating Whiteboard tags to Keywords: (EasyHack DifficultyInteresting SkillCpp)
JanI is default CC for Easy Hacks (Add Jan; remove LibreOffice Dev List from CC)
On Windows, we use dialogs provided by system TWAIN DSM. We can't add
a "Scan" button to the "Select source" dialog; but it's reasonable to
assume that user would select a scanner to scan, so let's proceed to
scan when user confirms selection in the dialog.
Mike Kaganski committed a patch related to this issue.
It has been pushed to "master":
tdf#42075: Perform scan after selecting a scanner on Windows
It will be available in 6.3.0.
The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
Affected users are encouraged to test the fix and report feedback.