I have a form containing some controls xamEditors. This blank form is loaded and the user should fill it. However, the user can confirm even without filling anything. How do I use the validation of xamEditor if the user confirms me a blank form considering the fact that yours controls do not trigger the validation if you do not take the focus?
Thanks for reply
I'm not sure what you mean by our controls do not trigger validation. Are you saying that you have some other standard wpf controls that behave differently than our with regards to validation of bound properties? If so please provide an example and we can look into why that is. If you want to see if the Value of the editors are considered valid, you can check their IsValueValid property.
I try to explain better. I have a form with three XamTextEditor wich have <ValueConstraint Nullable="False">. My form looks like this:
In this case (the form is empty) if I press the button I don't receive errors and IsValueValid property is set to true. How do I cause validation?
With regards to the button, there is no relationship between the editor controls and the button just as there wouldn't be with any other WPF control so I'm not sure how you are expecting our controls to play a role here.
With regards to the IsValueValid, it's probably only set when the value has changed so if the starting value is the default value it wouldn't have changed and the IsValueValid wouldn't have been evaluated. We should probably validate the value based on the constraints to initialize the IsValueValid. I submitted an issue for that portion.
Andrew Smith"] We should probably validate the value based on the constraints to initialize the IsValueValid. I submitted an issue for that portion.
We should probably validate the value based on the constraints to initialize the IsValueValid. I submitted an issue for that portion.
Fixing this would be enough to solve my problems.
Is this proplem solved ?
If you mean the issue regarding the IsValueValid being initialized based on the original value then yes this has been resolved in a recent hotfix as well as being part of the 9.2 release version.