A control toolkit for Windows 8 XAML applications. Contains some UI controls to make it easier to create Windows UI style apps for the Windows Store in accordance with Windows UI guidelines.
When the user manually changes the number (through use of the keyboard as opposed to the increment/decrement buttons) and then uses the increment or decrement button you are able to set a number outside that of the minimum and maxmimum constraints.
Consider Minimum=5 and Increment=5. The user types the number 9 into the text box. The user then uses the decrement button which is not disabled and gives the value 4. The user can then continue to decrement as much as they wish.
I think the bug is that SetValidIncrementDirection() only checks whether the value has reached the minimum or maximum, not whether another increment or decrement would result in a number outside of these constraints?
When the user manually changes the number (through use of the keyboard as opposed to the increment/decrement buttons) and then uses the increment or decrement button you are able to set a number outside that of the minimum and maxmimum constraints.
Consider
Minimum=5andIncrement=5. The user types the number9into the text box. The user then uses the decrement button which is not disabled and gives the value 4. The user can then continue to decrement as much as they wish.I think the bug is that
SetValidIncrementDirection()only checks whether the value has reached the minimum or maximum, not whether another increment or decrement would result in a number outside of these constraints?