gscan2pdf / Bugs / #211 Current version: does not start scanner detection

#211 Current version: does not start scanner detection

Milestone: v1.0_(example)

Status: closed-fixed

Owner: nobody

Labels: None

Priority: 5

Updated: 2015-10-05

Created: 2015-10-01

Creator: Wikinaut

Private: No

361dcf75198f9def03bb9dbcfa28022f06470d20 is the last commit, which works on my i5 (2core/4thread) CPU i5 4250U https://www-ssl.intel.com/content/www/us/en/nuc/nuc-kit-d54250wykh.html

Next commit does not start the scanner detection.

Discussion

Wikinaut - 2015-10-02

This window is shown when I click onto "scan"

in all versions after 361dcf75198f9def03bb9dbcfa28022f06470d20

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Jeffrey Ratcliffe - 2015-10-04

Fixed in 1c1e257f. Thanks for the report.

Last edit: Jeffrey Ratcliffe 2015-10-04

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Jeffrey Ratcliffe - 2015-10-04

status: open --> closed-fixed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Wikinaut - 2015-10-04

I confirm, that this is fixed now (and scanning works).

However, after gscan2pdf has found the device, there is a new status message shown, which is not automatically deleted:

"Option resolution wird eingestellt."

I don't know what exactly is meant. whether it is a bug or what else - perhaps you mean that the Scan Mode Settings are now opened and the user can start scanning?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Jeffrey Ratcliffe - 2015-10-04

I agree that the message is misleading. In your case, it looks like a poor translation. The English would be something like "setting option resolution" and is meant as a progress report in case the process takes more than half a second.

Last edit: Jeffrey Ratcliffe 2015-10-04

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Wikinaut - 2015-10-04

I don't understand. Is the message related to a (programatic) setting of the scanner, or is it related to the Mode Setting Dialog Window (where the user can modify the parameters ?)

If case 1, then that's in my view a bug, because the message is not cleared (it should be cleared after a while). On my system, it stays until I actually start scanning. Only opening the Mode Setting Dialog Window does not clear the message.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Jeffrey Ratcliffe - 2015-10-04

It's a bug. The message should be cleared. It looks as though the code clearing it is being excuted too early.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Jeffrey Ratcliffe - 2015-10-05

I've just pushed a fix.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.