On Dec 16, 2008 1:17pm, "m. allan noah" wrote:
> what backend and scanner is this?
> > $ frontend/scanimage -d test -t 1 -l 2 -x 21 -y 32 --batch-count=2 -v
-v -v
ie the test backend.
Regards
Jeff
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.a
yes- it seems there is an extra -1, I don't understand why they are
even there. I'll commit a fix this afternoon.
allan
--
"The truth is an offense, but not a sin"
what backend and scanner is this?
allan
On Tue, Dec 16, 2008 at 2:11 AM, wrote:
> On Dec 13, 2008 2:41pm, "m. allan noah" wrote:
>> can you verify that the version of scanimage that is in sane CVS now
>> fixes the complaining?
>
> No:
>
> $ frontend/scanimage -d test -t 1 -l 2 -x 21 -y 32 --ba
On Dec 13, 2008 2:41pm, "m. allan noah" wrote:
> can you verify that the version of scanimage that is in sane CVS now
> fixes the complaining?
No:
$ frontend/scanimage -d test -t 1 -l 2 -x 21 -y 32 --batch-count=2 -v -v -v
lt-scanimage: value for --tl-y is: 1
lt-scanimage: value for --tl-x is: 2
On Wed, Dec 10, 2008 at 2:20 AM, Jeffrey Ratcliffe
wrote:
> 2008/12/10 m. allan noah :
>> No, they are not floats, they are fixed. It is possible to manipulate
>> them without UNFIXing them. The fujitsu backend has produced these
>> type of warnings for years, even on simple things like
>> --resol
2008/12/10 m. allan noah :
> No, they are not floats, they are fixed. It is possible to manipulate
> them without UNFIXing them. The fujitsu backend has produced these
> type of warnings for years, even on simple things like
> --resolution=100, and I never could figure out why, until now...
Of cou
On Thu, Nov 13, 2008 at 4:26 PM, Jeffrey Ratcliffe
wrote:
>> then, under the hood, scanimage converts your commands like so:
>>
>> -l 2 -x 21 = --tl_x 2 --br_x 23
>> -t 1 -y 32 = --tl_y 1 --br_y 33
>
> The relevant line is 2038:
>
> val = pos + window_val[index] - 1;
>
> But these are
> then, under the hood, scanimage converts your commands like so:
>
> -l 2 -x 21 = --tl_x 2 --br_x 23
> -t 1 -y 32 = --tl_y 1 --br_y 33
The relevant line is 2038:
val = pos + window_val[index] - 1;
But these aren't integers, they are floats, so I don't think the above
is correct. T
I've finished transliterating scanimage and scanadf into Perl.
Everything works as in the original apart from a funny discrepancy:
$ scanimage -d test -t 1 -l 2 -x 21 -y 32 --batch-count=2 -v -v -v
gives me in 1.0.19:
scanimage: value for --tl-y is: 1
scanimage: value for --tl-x is: 2
scanimage:
On Tue, Nov 11, 2008 at 3:11 PM, Jeffrey Ratcliffe
wrote:
> I've finished transliterating scanimage and scanadf into Perl.
> Everything works as in the original apart from a funny discrepancy:
>
> $ scanimage -d test -t 1 -l 2 -x 21 -y 32 --batch-count=2 -v -v -v
>
> gives me in 1.0.19:
>
> scanim
2008/10/23 m. allan noah :
>> I'm thinking that adding opt->max_vals might be best, as defining
>> something like SANE_Word_sizeof just feels hackish.
>
> yes, i guess you'd have to do sizeof in your XS, and wrap it in a new
> member. either that, or your convert it to a pre-allocated perl array,
>
2008/10/21 m. allan noah :
> the option is a C-style array of values, not just a single value. lots
> of other backends do this too, search for GAMMA_VECTOR.
OK. I am with you now.
Is
opt->type != SANE_TYPE_STRING && opt->size
> (SANE_Int) sizeof (SANE_Word)
the only way for the fr
2008/10/20 m. allan noah :
> that is used when the option is a series of numbers. sometimes used
> for gamma tables and the like.
Can you be a bit more specific, perhaps with an example?
Thanks
Jeff
umax_pp.c: dev->opt[OPT_GAMMA_VECTOR].size = 256 * sizeof (SANE_Word);
the option is a C-style array of values, not just a single value. lots
of other backends do this too, search for GAMMA_VECTOR.
allan
On Tue, Oct 21, 2008 at 11:59 AM, Jeffrey Ratcliffe
wrote:
> 2008/10/20 m. allan noah :
>>
2008/10/15 Jeffrey Ratcliffe :
> The Perl bindings are more or less finished. I'm just transliterating
> scanimage and scanadf into Perl for checking purposes.
>
> It struck me that there was a potential infinite loop in the test mode
> in scanimage, so I've attached a patch to fix it.
>
> Also, I'
The Perl bindings are more or less finished. I'm just transliterating
scanimage and scanadf into Perl for checking purposes.
It struck me that there was a potential infinite loop in the test mode
in scanimage, so I've attached a patch to fix it.
Also, I'm trying to see the logic of the use of the
abel deuring writes:
> On 02.09.2008 07:25, Jeffrey Ratcliffe wrote:
>>
>> Is there a good reason why pkg-config files aren't built with SANE?
>> The lack of them make dependency checking difficult before build-time.
>
> I think nobody yet bothered about that.
There is a sane-config utility tha
2008/9/2 abel deuring :
> I would not mind seeing Perl bindings included. But other Sane folks
> should give their opinion too. I could imagine that CPAN might be a
> better place for the bindings, since Perl developers might look for Perl
> modules there, I'd guess. (disclaimer: I am not a Perl de
On 02.09.2008 07:25, Jeffrey Ratcliffe wrote:
> 2008/9/1 abel deuring :
>> The test backend is a invaluably useful tool for testing: You get more
>> or less any sort of device options; you can see if your bindings
>> properly handle things like enabling/disabling of options, if you get
>> the type
we have found that previous bindings that are included with sane are
often not kept up-to-date by their authors, not installed by the
distro vendors, and reimplemented by folks in their respective
communities. I think outside hosting makes more sense.
a patch for pkg-config would be accepted, if i
2008/9/1 abel deuring :
> The test backend is a invaluably useful tool for testing: You get more
> or less any sort of device options; you can see if your bindings
> properly handle things like enabling/disabling of options, if you get
> the type conversion between Sane and Perl data types properly
On 01.09.2008 10:56, Jeffrey Ratcliffe wrote:
> I am in the process of writing some Perl bindings for SANE.
>
> Would you like this to be a part of the SANE project, or should I
> start a new project (probably on Alioth)?
>
> It is tricky testing things, given the necessity for the correct
> hard
I am in the process of writing some Perl bindings for SANE.
Would you like this to be a part of the SANE project, or should I
start a new project (probably on Alioth)?
It is tricky testing things, given the necessity for the correct
hardware. How does SANE handle tests?
Regards
Jeff
23 matches
Mail list logo
