Assume you have a default range and an incremental range bound to the same node. Set the value of the default range to a new value. Click on the incremental range to set a third different value. There will be an artifact left on the incremental range. The problem is that when the focus changes from the non-incremental to incremental range due to the mouse click, the bound node will get the value of the non-incremental range. The incremental change will then get the value of the bound node. When the mouse down event is handled, the slider is erased from the position of prevX. However, prevX will reflect the INITIAL value of the incremental slider, not the current value, so we are erasing a slider that doesn't exist and we leave around the current slider.

fixed this by setting prevX to null on mouseup and upon initialization. And at mousedown when prevX isn't set, then I initialize it to the x position that corresponds to the current slider value.

Looks right, do you need in "dump" calls and should you null prevX on 'mouseup' event (I doubt since 'handler' object is recreated for every 'mousedown' event)? Today later I'll look more precisely.

Sorry, I should have made sure that I had all of the dumps out of there. You are also right in that we don't need to set it to null on mouseup.

checked into trunk

checked into 1.8.0 branch on 2006/10/11

checked into 1.8 branch on 2006/11/21