Added warning when min_value of range <= 0 while exp_edit is true.

[Piet-G]

Added warning when min_value of range is smaller or equal to 0 while exp_edit is true.
The new warning is: "If exp_edit is true min_value must be > 0."

This should make it more clear, see #21923

[ghost]

@dualmatrix i think there is something else going on here.
because, I just tested the example in 3.0.6.
the value performs perfectly fine if it goes to 0, even when exp_edit is enabled. i believe something was changed from 3.0.6 to 3.1 (the root issue)

[Piet-G]

@girng I'm just going by the docs which state that the value must be > 0

[ghost]

the docs say the min_value must be greater than 0. the value is bugged if it's set to 0, when exp_edit is enabled in 3.1. that's not the case in 3.0.6

[Piet-G]

@girng The bug with value only occurs when min_value is <= 0 and exp_edit is true otherwise it works fine.

[Piet-G]

I took a look at the 3.0 code and previously exp_edit was just ignored if min_val <= 0.
I'm not sure which behavior is preferred. Displaying a warning seems more logical to me.

[ghost]

@girng The bug with value only occurs when min_value is <= 0 and exp_edit is true otherwise it works fine.

That's what I thought was normal (not a bug)... okay, well a lot of game projects who will move from 3.0.6 to 3.1 will most likely need to adjust this then :P

but yeah,i agree, a warning would be best. instead of this bad polygon! stuff that i got lolz

[Piet-G]

@girng exp_edit is not enabled by default right? So this would only be an issue for those who accidentally enabled exp_edit and in that case the warning should be clear enough.

[ghost]

@girng exp_edit is not enabled by default right? So this would only be an issue for those who accidentally enabled exp_edit and in that case the warning should be clear enough.

yeah, that's true. thank you for looking into this btw, should be sufficient

[akien-mga]

Thanks!