BSlider order of operations issue when value 0

[kallisti5]

I noticed this through the DriveSetup app.

1) Create a new partition. 2) Slide the size to the right (max) 3) Take note of the size in the text box and label. (correct) 4) Slide the size down to 0. 5) The TextControl is the correct size (0) while the label at the top is a random size. 6) Sliding over and over to the minimum results in a wide range of numbers as the "minimum" size.

During the slide, Size() in Support.cpp SizeSlider is equal to the random number. SetSize however is equal to the correct "0" value at min.

I feel like this could be an ordering issue when setting values / calling the BMessage for modification of value.

What's odd is the max value seems to work consistently.