🚀 go-pugleaf

I just found out the hard way that if you use a minimum value when setting up an integerTextbox in a dialog (or any of the value-aware text or combo boxes), it automatically activates the maximum value, too.

So, if you're working with positive numbers, you'd better set both values or, as I did, you'll have the dialog checking for values in the range 1 to 0. It took me longer than you might think to resolve this because if you setup the element in a single statement, the runtime error is rather generic, so it's not clear what's wrong.

I finally twigged the problem when I moved setting the value to a second line of script and it gave me an explicit error message that indicated that it thought the maximum value was zero when I had not actually set a maximum value.

This happened to me using JavaScript, but I expect it is an issue in any of the languages.

Dave