Hello,
i use IG 15.1 and the issue describe in this thread is not fixed.
I also attach an exemple .
Any help would be appreciated!
Pierre
Hello Andrew,
Thanks for your support. In fact implementing IDataError is the easiest way to modify the error message ;)
Thanks.
Hello Pierre,
I am glad that 15.2.20152.1000 fixed the issue you were seeing.
The tooltips that you are seeing in the error message come from the Validation.Errors collection that exists on the XamNumericInput. The inputs use a converter internally to try to convert the value entered into the input to the type expected by it. As it cannot convert a blank value into a numeric one, you are seeing this error.
To change it, you will need to modify the ValidationDecorator object that owns this tooltip that shows this error message. I would recommend including the default style for ValidationDecorator to do this. In the control template for this element, you will see a tooltip. I would recommend placing a converter on the Content property of this tooltip so that you can change the displayed error message when the conversion fails.
Just as a side note, you can also personalize your own error messages for custom error conditions by implementing the IDataErrorInfo interface on your data item. I have attached a modified version of the sample project you have sent to demonstrate these two above things. The IDataErrorInfo implementation is on the top XamNumericInput and does not allow a value less than 10 or a custom error message is shown.
Please let me know if you have any other questions or concerns on this matter.
Sincerely,AndrewAssociate DeveloperInfragistics Inc.www.infragistics.com/support
With the version 15.2.20152.1000 the issue was fixed :)
Can i personalize the error message? ("The value '' can not converted) ? How?
thanks for your reply, my version is IG 15.1.20151.1000. Perhaps with this version the issue was not fixed. I will upgrade my version to the latest version (IG 15.2).
Thank you for your post!
I have been testing the sample application you have provided, but I can't seem to reproduce this behavior you are seeing. I have tried deleting the value and exiting both inputs, but when I set the value, either by usage of the spin buttons or by typing, the error message disappears on my end. My tests were made using the latest version of our 15.1 suite of WPF controls; specific version 15.1.20151.2122. The reason I ask this specifically is because I see that in the other forum thread, you reported that in version 14.2.20142.2224, this issue was fixed. Does the specific assembly version I mentioned above (15.1.20151.2122) match the ones you are using?