[sane-devel] sane_control_option question

[Fred Odendaal]

Thanks for the explanation Oliver. Is this documented anywhere? Do all 
the frontends behave the same way in response to bind-resolution?

My backend only supports the following resolutions in dpi:
75x75,
150x150,
300x300,
600x600,
600x1200

Therefore, I'll probably just use the resolution option. I was hoping to 
be better than the Windows driver and somehow relay information to the 
user that when they select 1200dpi they are really getting 600dpi x 
1200dpi. I suppose I'll just put that information in the man page.

Keep up the good work on xsane. It's a terrific front-end.
Fred.

Oliver Rauch wrote:

>Am Mon, 2005-10-17 um 19.58 schrieb Henning Meier-Geinitz:
>  
>
>>Hi,
>>
>>On Sun, Oct 16, 2005 at 06:15:24PM -0400, Fred Odendaal wrote:
>>    
>>
>>>Yes, I'm also quite surprised. It works fine with xscanimage, but 
>>>doesn't when I use xsane. So I compared the debug output.
>>>      
>>>
>>Strange. Maybe Oliver Rauch can comment on this?
>>
>>    
>>
>
>XSane tries to care about x-resolution, y-resolution and common
>resolution options. When the backend tries to automaitcally set
>y-resolution when x-resolution was changed this can interfere with the
>xsane functions and it also is no good idea.
>
>When the backend wants to make available a common resolution and
>separate x- and y- resolution options then it should create three
>resolutions options and on selection which of these are enabled:
>
>resolution (range or list)
>x-resolution (range or list)
>y-resolution (range or list)
>bind-resolution (boolean: enabled or disabled)
>
>with bind-resolution enabled only resolution is enabled and defines
>x- and y-resolution
>
>with bind-resolution disabled only x-resolution and y-resolution is
>enabled.
>
>Oliver
>
>
>
>  
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20051018/783361b4/attachment.html