I'll strip the code down later/tomorrow so I can test it - initialising to zero sounds like a promising candidate though - it does indeed check to see if the value has changed. One thing I did notice in there was that it used functions to get the max and min value, seems to me even just buffering these values would offer a slight performance increase - negligible granted, may changes like this across the board would make haiku even zippier than it already is! On 20 March 2010 00:04, Fredrik Holmqvist <fredrik.holmqvist@xxxxxxxxx> wrote: > 2010/3/19, Stephan Assmus <superstippi@xxxxxx>: >> I think he means sliding it all the way to the left. It sounds to me like >> an internal state is not updated. Like when you create the BSlider, it will >> have a value of 0, and then programatically setting another value will >> somewhere not cause an adjustment, and when you drag all the way to the >> left, it thinks nothing changed and doesn't fire. From there on, everything >> seems to be in sync. Something like that... >> > > Example for me with mouse prefs: > Acceleration slider starts at the middle. > Grab it and slide it to the left and move mouse out of the view or window. > Stop holding slider. > Exit app. > Start app. > It's still in the middle. > > /Fredrik Holmqvist, TQH > >