Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
NumericUpDown is bound to byte?, Minimum = 0 and Maximum = 255. If value decrements to 0, the Button is disabled, but with MouseWheel it is possible to decrement more.
Next issue is, that the value is parsed immediatly:
None of this issues are seen in 1.6.0-alpha011.
Regarding the MouseWheel issue: I've downloaded the sources yesterday and bound the Value property of the NUD to the TestValue. Minus button is disabled, because we're at the Minimum. So far, so good. But if I use the MouseWheel, the TestValue gets decremented to -1 and my ViewModel has the wrong value. The NUD still shows 0.
If the NUD then loses the focus, the TestValue will be updated to 0. But my own expectation of such an control is, that the (bound) Value should never fall below the Minimum.