Hi,
On Tue, Dec 10, 2002 at 01:03:00PM -0500, Matto Marjanovic wrote:
> >If I understand correctly what happens in the case of auth_callback,
> >the remote sane_func isn't finished yet, the callback is still running.
> >
> >> o Network backend calls the client frontend's callback with string
Good morning,
>If I understand correctly what happens in the case of auth_callback,
>the remote sane_func isn't finished yet, the callback is still running.
>
>> o Network backend calls the client frontend's callback with string,
>> then finally returns from "sane_func()" request.
Hi,
On Mon, Dec 09, 2002 at 04:39:54PM -0500, Matto Marjanovic wrote:
> (For those who've lost track: "this method" is to use struct, containing
> both the status code and a verbose string pointer, as the return value of
> all the sane_() functions.)
>
> Um, except now a string has to be marsh
>From: Diego Zuccato
>Date: Mon, 09 Dec 2002 00:13:01 +
>
>Henning Meier-Geinitz wrote:
>
>> And this would be returned by any SANE API function that currently
>> returns SANE_Status? Nice, because it links the error number and the
>> message. No need for an extra call to a function.
Henning Meier-Geinitz wrote:
> And this would be returned by any SANE API function that currently
> returns SANE_Status? Nice, because it links the error number and the
> message. No need for an extra call to a function.
Yep. That's why I like this method. :-)
> However: How long is errmsg valid?
Hi,
On Sun, Dec 08, 2002 at 01:14:35PM +, Diego Zuccato wrote:
> Henning Meier-Geinitz wrote:
>
> > So the backend would call the callback immediatly, when a fatal error
> > occurs. Fatal means, that it will return anything other than
> > SANE_STATUS_GOOD. This would work for command-line pro
Henning Meier-Geinitz wrote:
> So the backend would call the callback immediatly, when a fatal error
> occurs. Fatal means, that it will return anything other than
> SANE_STATUS_GOOD. This would work for command-line programs but may be
> messy for graphical frontends.
Errr... Since you're definin
Hi,
On Sat, Dec 07, 2002 at 01:19:31PM +1100, Matthew Duggan wrote:
> > 4.3.16 sane_verbose_error
> >
> > This function returns a verbose description of the latest error. The
> > returned string consists of one or more complete sentences. It is the
> > responsibility of the frontend to break the s
Hi,
Henning Meier-Geinitz wrote:
...
> Proposal:
>
> 4.3.16 sane_verbose_error
>
> This function returns a verbose description of the latest error. The
> returned string consists of one or more complete sentences. It is the
> responsibility of the frontend to break the string into
> managable-len
Hi,
On Fri, Dec 06, 2002 at 10:43:33AM +0100, Enno Fennema wrote:
> A few years ago James W. McAllister, a Scottish philosopher at the time
> working at Leiden University, wrote a book called "Beauty and Revolution
> in Science". He noted that scientists in choosing between competing
> theories ar
"Matthew Duggan" wrote:
>> SANE_String_Const sane_verbose_error(Sane_Handle h)
>I like this, and it's pretty much what I was looking for. I only have
>one criticism from a backend writing point of view: What happens if the
>only return has been SANE_STATUS_GOOD? Maybe just:
>-
>This function
Hi,
On Fri, Dec 06, 2002 at 10:00:12AM +1100, Matthew Duggan wrote:
> Henning Meier-Geinitz wrote:
> > > In my view sane_strstatus() is a sanei_ rather than a sane_
> function.
> >
> > It's an interface between the frontend and the backend. The frontend
> > asks the backend about the textual mean
Thanks for reply on 1. I have no very strong feelings on points 3) to 5)
but have to come back on 2).
A few years ago James W. McAllister, a Scottish philosopher at the time
working at Leiden University, wrote a book called "Beauty and Revolution
in Science". He noted that scientists in choosing b
Hi,
Henning Meier-Geinitz wrote:
> > In my view sane_strstatus() is a sanei_ rather than a sane_
function.
>
> It's an interface between the frontend and the backend. The frontend
> asks the backend about the textual meaning of an error.
> The function is also used in the backends but the idea is
[cut]
> 6) Configuration files
> Agree a format for a standard /etc/sane.conf file.
> Could by commandline option use other path, etc.
>
> Backends need at least a method to derive the name of the device as used
> by the operating system but could benefit from some configuration
> information, cal
Hi,
On Wed, Dec 04, 2002 at 11:08:31AM +0100, Enno Fennema wrote:
> I would like to make some comments on the SANE 2.06 draft standard.
Thanks for your comments. I hope I can put some more time into SANE2
during the next days.
> They represent my personal preferences and proposals and are offere
On Wednesday 04 December 2002 11:08, Enno Fennema wrote:
> 2) SANE_Handle
> A SANE_Handle points to a very important structure, viz.
I do not see an advantage of this and I do not see a reason to do any cha=
nges=20
here. The way sane1 does handle it does work.
The sane standard is defined as a f
I would like to make some comments on the SANE 2.06 draft standard.
They represent my personal preferences and proposals and are offerered
for discussion but rather than prefixing each statement with 'I
think...' 'I propose...' etc.
They are presented as statements of fact, which they are not.
So
18 matches
Mail list logo
