On Tue, 2 Jun 2009 06:43:18 +0200
stef wrote:
> > > what will the front-end do with that info? just plow ahead and ignore
> > > it? Thats not really a status, but more of a param of the image data.
> > > I think if you want that info, it makes more sense to turn the last
> > > frame member of san
Le lundi 1 juin 2009 22:13:00 Alessandro Zummo, vous avez ?crit :
> On Mon, 1 Jun 2009 15:14:05 -0400
>
> "m. allan noah" wrote:
> > what will the front-end do with that info? just plow ahead and ignore
> > it? Thats not really a status, but more of a param of the image data.
> > I think if you wa
On Mon, 1 Jun 2009 15:14:05 -0400
"m. allan noah" wrote:
> what will the front-end do with that info? just plow ahead and ignore
> it? Thats not really a status, but more of a param of the image data.
> I think if you want that info, it makes more sense to turn the last
> frame member of sane_par
Le lundi 1 juin 2009 21:14:05 m. allan noah, vous avez ?crit :
> On Mon, Jun 1, 2009 at 3:08 PM, stef wrote:
...
> >
> >I think a SANE_STATUS_UNCALIBRATED would also be useful. It would
> > let a frontend that the scan can start, but will be uncalibrated. This
> > would fit in the case of
Le vendredi 29 mai 2009 22:23:23 m. allan noah, vous avez ?crit :
> well, lets re-open the discussion of the return codes. Julien had some
> reservations about this technique. I dont have a problem with it, as
> long as we formalize it in the standard exactly which status codes
> require retry. I a
On Mon, Jun 1, 2009 at 3:08 PM, stef wrote:
> Le vendredi 29 mai 2009 22:23:23 m. allan noah, vous avez ?crit :
>> well, lets re-open the discussion of the return codes. Julien had some
>> reservations about this technique. I dont have a problem with it, as
>> long as we formalize it in the standa
"m. allan noah" writes:
> On Sun, May 31, 2009 at 7:23 PM, Olaf Meeuwissen
> wrote:
>> "m. allan noah" writes:
>>
>>> [snip]
>>> I also would like to add a generic 'SANE_STATUS_RETRY' for those cases
>>> where the backend has to block during sane_start because it must
>>> ingest the entire imag
"m. allan noah" writes:
> [snip]
> I also would like to add a generic 'SANE_STATUS_RETRY' for those cases
> where the backend has to block during sane_start because it must
> ingest the entire image before the size is known.
The standard allows backends to return an unknown height, so what kind
On Sun, May 31, 2009 at 9:14 PM, Olaf Meeuwissen
wrote:
> "m. allan noah" writes:
>
>> On Sun, May 31, 2009 at 7:23 PM, Olaf Meeuwissen
>> wrote:
>>> "m. allan noah" writes:
>>>
[snip]
I also would like to add a generic 'SANE_STATUS_RETRY' for those cases
where the backend has to
On Sun, May 31, 2009 at 7:23 PM, Olaf Meeuwissen
wrote:
> "m. allan noah" writes:
>
>> [snip]
>> I also would like to add a generic 'SANE_STATUS_RETRY' for those cases
>> where the backend has to block during sane_start because it must
>> ingest the entire image before the size is known.
>
> The
On Fri, 29 May 2009 16:23:23 -0400
"m. allan noah" wrote:
> well, lets re-open the discussion of the return codes. Julien had some
> reservations about this technique. I dont have a problem with it, as
> long as we formalize it in the standard exactly which status codes
> require retry. I also wo
On Fri, 29 May 2009 16:18:07 -0400
"m. allan noah" wrote:
> they are not enums in current git tree.
I know, but it's guaranteed they will not be converted to enums?
--
Best regards,
Alessandro Zummo,
Tower Technologies - Torino, Italy
http://www.towertech.it
well, lets re-open the discussion of the return codes. Julien had some
reservations about this technique. I dont have a problem with it, as
long as we formalize it in the standard exactly which status codes
require retry. I also would like to add a generic 'SANE_STATUS_RETRY'
for those cases where
they are not enums in current git tree.
allan
On Fri, May 29, 2009 at 9:29 AM, Alessandro Zummo
wrote:
> On Fri, 29 May 2009 15:04:53 +0200
> Alessandro Zummo wrote:
>
>> ?Hi, I have a couple of issues on the epson2 driver
>> ?which can easily be resolved by using the warming up return
>> ?code
On Fri, 29 May 2009 15:04:53 +0200
Alessandro Zummo wrote:
> Hi, I have a couple of issues on the epson2 driver
> which can easily be resolved by using the warming up return
> code.
>
> Maybe we can have a new branch on the git repo
> as suggested by Alesh ?
btw we also need some #define
Hi, I have a couple of issues on the epson2 driver
which can easily be resolved by using the warming up return
code.
Maybe we can have a new branch on the git repo
as suggested by Alesh ?
--
Best regards,
Alessandro Zummo,
Tower Technologies - Torino, Italy
http://www.towertech.
16 matches
Mail list logo
