This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
My source is a bit out of date, so please forgive me if this has been solved already. Validation is happening at the wrong time with the IntegerTextBox. The control is overriding OnPreviewTextInput, and doing its checks at that point. The result is that if the minimum is 3 and the maximum is 12 you can't type in a value of 12 because you're thwarted every key press. The filtering should only happen when the control is about to push a value through the binding to the view model. Maybe you could use validators? This seemed to work pretty well for me. |
|
|
|
|
We added a RangeConstraintMode property a few months back. If you set this to OnLostFocus or OnLostFocusOrReturn, the control will only perform range checking when the user leaves the control. This isn't quite the same as the solution you identify but in practice I think it should address your problem. This should be in all nightly builds since late February or thereabouts. Let us know if you need something different / more. |
|
|
|
