On 7/22/08, m. allan noah wrote:
> Several backends use SANE_NAME_SCAN_X_RESOLUTION: abaton, artec,
> canon, epjitsu, fujitsu, microtek2, sp15c, and umax. I propose to
> change those backends to use SANE_NAME_SCAN_RESOLUTION, so that their
> UI does not change if we separate those options.
>
i
Several backends use SANE_NAME_SCAN_X_RESOLUTION: abaton, artec,
canon, epjitsu, fujitsu, microtek2, sp15c, and umax. I propose to
change those backends to use SANE_NAME_SCAN_RESOLUTION, so that their
UI does not change if we separate those options.
comments?
allan
On Wed, Jul 9, 2008 at 11:57 P
i actually just found this comment in maxview, so other folks have
noticed this too...
//actually there seems to be no difference between
//resolution and x-resolution; see saneopts.h
allan
On 7/9/08, Olaf Meeuwissen wrote:
> "m. allan noah" writes:
>
> > On 7/8/08, Olaf Meeuwissen wrote:
>
"m. allan noah" writes:
> On 7/8/08, Olaf Meeuwissen wrote:
>> Checking out why setting X/Y resolutions independently didn't quite
>> work as expected, I discovered that saneopts.h has this:
>>
>> #define SANE_NAME_SCAN_RESOLUTION "resolution"
>> #define SANE_NAME_SCAN_X_RESOLUTION "r
Checking out why setting X/Y resolutions independently didn't quite
work as expected, I discovered that saneopts.h has this:
#define SANE_NAME_SCAN_RESOLUTION "resolution"
#define SANE_NAME_SCAN_X_RESOLUTION "resolution"
#define SANE_NAME_SCAN_Y_RESOLUTION "y-resolution"
That means
On 7/8/08, Olaf Meeuwissen wrote:
> Checking out why setting X/Y resolutions independently didn't quite
> work as expected, I discovered that saneopts.h has this:
>
> #define SANE_NAME_SCAN_RESOLUTION "resolution"
> #define SANE_NAME_SCAN_X_RESOLUTION "resolution"
> #define SANE_NAME_
