On Tue, Nov 4, 2008 at 5:22 PM, Julien BLACHE <jb at jblache.org> wrote: > "m. allan noah" <kitno455 at gmail.com> wrote: > > Hi, > >> damnit julien- it is called sane_status!, you dont get to declare that >> 'its not really a status, so lets not put statuses in it' it is just >> like SANE_STATUS_BUSY, where a backend might very well choose to retry >> after a few seconds. > > Hmm, SANE_STATUS_DEVICE_BUSY is actually often returned when the USB > device cannot be opened because it's already in use by another > process. > > I do make a difference between operation status and hardware status, > and looking at SANE_Status, there's just nothing like the "warming up" > thing in there at the moment. Though I concede that a couple of things > are borderline. > > Maybe I should not try to put some sanity into SANE. >
Sanity is not the problem. The extreme need to make a release, coupled with limited developer resources is the problem. Lets bump the version everywhere to 2. allan -- "The truth is an offense, but not a sin"
