I'm Aceifying some of my addons and this is my first go (in years, I guess) with using Ace so I prettymuch have to re-learn it all.
I'm SetPoint'ing my default unitframes based on a db value set using AceConfig(GUI) and I'm getting some weird behaviour. the Y slider has the range -500 to 500 and when I move the slider up from -500 to 500 it stops at 50% and snaps back to -500.
at line 157 I have a print that prints the value that the setter is getting and that's just -500 on my screen if I move the slider over 50%. I can still use the value input of the slider to set the value above 0.
if it would default to a value then you would have a very hard time getting max precision between numbers as such leaving it off and allowing you to set your own step is the best solution atm.
as for it not working correctly i don't know i have never had a problem with it (with step and without)
If no "min" or "max" are specified, the manual input of the range control will accept any and all values!
step - step value: "smaller than this will break the code" (default=no stepping limit)
Note that you can consider the fact that the author used defaults as an error checking condition to prevent crazy errors showing in the addon. Just because defaults were supplied that doesn't mean they shouldn't be entered.
I wouldn't personally agree that this is a bug. An alternative would have been for the lib author to throw an error if they weren't set. Which I suppose would have helped your cause as you'd have known sooner that the values should be specified.