sorry rene- this should have gone to list... On 5/26/08, m. allan noah <kitno455 at gmail.com> wrote: > On 5/26/08, Ren? Rebe <rene at exactcode.de> wrote: > > > Hi Allan, > > > > can you explain the paper width option to me? Why can we > > not simply use br x/y? > > > > Actually I got a Fujitsu scanner here and find the duplicate > > paper width option annoying at best. > > > it is not duplicate. it is used by the backend to properly center the > users x/y params to the moving paper guides. otherwise, if they want > to scan an entire sheet of A5, they have to set the tl_x/y to some > weird value that they have to calculate from the scanner's maximum > width. > how do you handle this in avision now? > > > > > > Aside the already mentioned button to use some more extend-able > > XML encoding instead of a hardcoded set, I wonder if it is > > good to expose sensors, frontends would rarely (if ever?) want > > to check for them explicitly and the backend must check the > > sensors before or during scan to generate proper errors > > accordingly anyway. > > > don't assume that sensors only indicate errors. the paper-in signal is > quite useful in high volume apps- the front-end can start scanning > immediately. > > xml does not fix this problem, cause we would still have to define a > schema so that front-ends could interpret it. so, lets just avoid the > xml dependency. > > > allan > -- > "The truth is an offense, but not a sin" >
-- "The truth is an offense, but not a sin"