muZZkat/NMRangeSlider — pull request #1 by Club15CC (2012-11-14 08:39:52+00:00)
Title: Quick Fix for Lower Value not set when Min Range is specified first...

In the setters, lowerValue depends on upperValue when minRange is set. If upperValue is still 0 then this causes lowerValue to not be set.

This commit is a quick fix (hack) that just calls setLowerValue a second time in the setLowerValue:upperValue method. It still doesn't solve the problem of the client using the properties to initialise the lower and upper values.

A better fix might be to have lower/upperValue initialise to -/+FLT_MAX or have lower value only adjust for minRange if (upperValue != some-pre-decided-init)...it's probably worth a bit more thought...

Thx for the component. I've given it 5 stars on CocoaControls :)