Bugfix, that allows setting max to 0

I spotted a bug, when setting the max to 0.
Since 0 is a falsy value, the maximum was represented as 100.