I thought of that, but I think that would be undesirable in about half the cases, where you actually want the function to not work, given that the "low" value is in this case greater than the "high" value. That was the purpose of the "real world" scenario.Are you suggesting that Rainmeter determine which of those two parameters is lowest and highest, then restrict x based on that?
I guess the point I was trying to make here is that in the case of such invalid order, the behavior of the function is inconsistent (i.e. sometimes it's choosing the "low" value aka the 2nd parameter, sometimes it's choosing the "high" value aka the 3rd parameter, in effect toggling between them in a somewhat arbitrary fashion).
Ideally, it should react "the same", or at least according to some logic, when the order is invalid. I just don't know what that logic should be, hence not being able to suggest an "expected" behavior and appealing to someone who can see things clearer in that regard.
Anyway, if you think otherwise, it's no problem. I was just trying to see if there was a way to avoid letting the user cover the possibility of the "low" being greater than the "high" by making the formulas longer, that's all.
P.S. Don't worry about the honesty, I always prefer it.
Statistics: Posted by Yincognito — Yesterday, 6:37 pm