> Another suggestion: Many scanners can return quite detailed error > information, like "lamp failure", "optical hardware error", "mechanical > hardware error", "5V fuse blown", "memory error" and whatever else. A > frontend could call a function like > > SANE_String sane_verbose_error(Sane_Handle h) > > to read some details about the last error. Printing this stuff might > save users a few gray hairs.
I second that. I have that problem too. What about a SANE_STATUS_HW_ERROR. A frontend would handle it like SANE_STATUS_IO_ERROR, but it would call a backend function that returns a string for the error and display it. Frank.
