# Re: mustek: timeout after scan and cmd line parser bug

David Mosberger-Tang (davidm@azstarnet.com)
Thu, 17 Jul 1997 09:19:18 -0700

- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
- Next message: Billy the expert skier!: "Re: sane v0.61 on SCO"
- Previous message: becka@sunserver1.rz.uni-duesseldorf.de: "Re: mustek: timeout after scan and cmd line parser bug"
- In reply to: becka@sunserver1.rz.uni-duesseldorf.de: "Re: mustek: timeout after scan and cmd line parser bug"

>>>>> On Thu, 17 Jul 1997 13:40:01 +0200 (MET DST), becka@sunserver1.rz.uni-duesseldorf.de said:

>> 2. While scanimage --mode color -y 100 does what I expected it
>> to, scanimage -y 100 --mode color results in a full 36cm scan (-y
>> 100 is ignored).

Andy> Yes - I have seen this, too. David seems to be very busy and
Andy> so am I with GGI. It is probably something quite simple. Maybe
Andy> you'd like to fix it ?

I know what's going wrong, but as you said, I'm unlikely to find time
to fix this real soon. What's happening is that switching the mode
causes all options to be re-fetched. As a result, the value set by -y
is lost when the --mode option is processed. It probably would be
best to stash away the values for -l, -t, -x, and -y and process them
only right before starting a scan. However, note that in general the
command-line options _are_ order-sensitive. Maybe the real bug is
that scanimage(1) doesn't explain this sufficiently well?

--david

    --
    Source code, list archive, and docs: http://www.azstarnet.com/~axplinux/sane/
    To unsubscribe: mail -s unsubscribe sane-devel-request@listserv.azstarnet.com

- Next message: Billy the expert skier!: "Re: sane v0.61 on SCO"
- Previous message: becka@sunserver1.rz.uni-duesseldorf.de: "Re: mustek: timeout after scan and cmd line parser bug"
- In reply to: becka@sunserver1.rz.uni-duesseldorf.de: "Re: mustek: timeout after scan and cmd line parser bug"