[sane-devel] Sane and HAL

[Martin Owens]

Where you have more than one model that has the same usb model and
manufacturer keys you should set the hal key to 'multiple' or some
kind of special key which tells it that it's not decided and could be
one of many things. it's important because it gives the user or client
software the choice of setting which actual model the scanner is which
sane currently prohibits without some serious stressful messing about.

But it seems like sane with mearly be providing information to hal and
sane will be keeping it's detection and use code together which I
don't think is the right way to move forward with hal support. :-/
perhaps I've seen it wrong

> But I don't know how to do it in HAL because I cannot have
> a model name string like "Epson Perfection 1250 Photo"
> as (part of) a key in HAL (like I did it to get the support
> status below the backend in the hierarchy).
>
>
>
> > > "HAL support in SANE" versus "SANE support in HAL":
> ...
> > I think it is better to keep the file in the Sane package.
>
> I fully agree.
>

The question is, what will you do for modified fdi files? will sane
recognise hal settings have been modified by the user for instance if
a user configures a new scanner to work with an existing backend?