InvalidValueBehavior="DisplayErrorMessage" : How to control the text displayed in the EditModeValidationError event?

State Suggested Answer
Replies 3 replies
Answers 1 answer
Subscribers 6 subscribers
Views 874156 views
Users 0 members are here

755

Karine posted over 14 years ago

Hi,

I'm using a XamDateTimeEditor and I specified a ValueConstraint in the xaml. I also specified InvalidValueBehavior="DisplayErrorMessage".

I dont want to show the default message. I want to control the message depending on the value specified. If it's over or lower... In the EditModeValidationError event, I only have acces to the original value. I dont see the new value. I tried to set the message to e.ErrorMessage = "";

and use the CellUpdated event to check the value, but its not called until the ValueConstraint is respected.

How can I access the old and new valeur of the cell to control the message displayed? Or is there a way to set the InvalidValueBehavior to none?

54937

Offline Andrew Smith [Infragistics] posted over 14 years ago in reply to Sylvain

With regards to the custom message - the string isn't hard coded so in theory you could localize that string within your app using our ResourceCustomizer. The strings resource names are values like LMSG_ValueConstraint_MaxExclusive.
Cancel
Reply

Cancel
470

Sylvain posted over 14 years ago in reply to Andrew Smith [Infragistics]

Thank you, that ansers my question perfectly.

Note that my application is supported in French and English so your custom message wont fit. And we also use a custom message window with our icons and stuff. The 9.2 release wont help resolve my issue.

Thanks anyway.
Cancel
Reply

Cancel
54937

Suggested Answer
Offline Andrew Smith [Infragistics] posted over 14 years ago

girardkarine said:
I dont want to show the default message. I want to control the message depending on the value specified. If it's over or lower... In the EditModeValidationError event, I only have acces to the original value. I dont see the new value.
Well if the value could be parsed then the Value property of the editor should be the current value. If the error occurred because the value could not be parsed then you might have to look at the Text property in the EditModeValidationError event and then set the e.ErrorMessage accordingly. Note I believe in 9.2 and later the error message when you have set the constraints will be more descriptive so if for example you had set the MaxExclusive to 150 and you entered 150 as the value in 9.1 the error message would have been something like "Value is invalid." but in 9.2 it will be something like "Value must be lessage than 150".

girardkarine said:
Or is there a way to set the InvalidValueBehavior to none?
There isn't a none because the editor must do something - revert to the old value or keep the invalid value and stay in edit mode but it can't leave edit mode in the invalid state.
Cancel
Reply

Reject Answer

Cancel