Matto> The backend suggestion is actually directly counter to what
Matto> is written in the API documentation for sane_control_option:
Matto> .....When this happens, the SANE backend sets this
Matto> member in *i to indicate that the application should reload
Matto> all options. __Note that this member may be set even if no
Matto> other option changed.__ However, it is guaranteed that other
Matto> options never change without this member being set.
Matto> Perhaps the API spec should be modified; either way, one of
Matto> the two above needs to be put in effect.
Yes, you are right, the backend is indeed the right place for this to
be fixed, since the frontend would have to be overly conserative
otherwise (it doesn't know which options might cause options to be
reloaded). I updated the documentation and the mustek, hp, and qcam
backends accordingly (for consistency's sake; those backends were not
actually affected by the apparent change in GTK callback behavior).
Thanks for tracking this down!
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail email@example.com