Hi Oliver, thanx for the info, I'll test it.. - sorry for the late repsonse.
On Tuesday 08 June 2004 15:44, Oliver Rauch wrote: [SNIPSNAP] > static void xsane_back_gtk_value_update(...) > > case SANE_TYPE_INT: > val = adj_data->value + 0.5; > > remove the "+ 0.5" and it should work. > > But I am not sure if this will cause other problems. > I think there has been a reason for adding the "+ 0.5" Probably yes ;-) but obviously the reason is not that important, that you've missed the comment on that workaround :-))) Ciao, Gerhard > > Oliver > > Am Die, 2004-06-08 um 12.15 schrieb Gerhard Jaeger: > > Hi, > > > > I'm currenlty trying to add more frontend configurable options to the > > Plustek backend and have some problems with xsane now. > > There's a value whose range is from -1..63. At the default state, when > > starting xsane, it is properly displayed: -1. > > When changing once to i.e. 6 and changing it back to -1, xsane stores > > it as 0 and also displays it after the next startup as 0.. > > Bug or feature? What is wrong. The type of this option is SANE_TYPE_INT, > > the contraint_type is SANE_CONTRAINT_RANGE... > > The configfile of xsane shows, that this value is stored as 0 and not as > > -1... > > > > Any ideas? > > Gerhard
