Hi,
I upgraded to 11.1 to 13.1, and a XamTextEditor I have that was previously working is showing the following behavior:
1) Enter edit mode by making the cell active or right clicking the cell and choosing rename
2) type in some random garbage
3) hit enter key OR change focus by hitting tab or clicking out
4) the entered value is immediately blanked out and validation fails turning the cell red
Is there some change moving from the IG versions that changes the way EditMode is handled?
Thanks for your help.
Edit: I did some more digging, the text box in the XamTextEditor control that holds the actual text value is fine through the EditModeEnding event, and then suddenly in EditModeEnded, the text box in the control is null.
Hello David,
Thank you for your post. I have been looking into it and I can say that there isn’t any breaking change in the XamTextEditor in version 13.1. I believe that the result you want to achieve is the same as the one in the sample in the Samples Browser under xamDataGrid / Display / IDataErrorInfo Support section. Please take a look at it and if it doesn’t satisfies all your needs, could you please send more details about the functionality you want to achieve and an isolated sample project, where your issue is reproduced, so I can investigate it further for you.
Looking forward for your reply.
Sorry, let me clarify. I want basic functionality - I want to hit enter, and have my value saved.
The behavior I am getting is not consistent with this, when I hit enter after making modifications to a field, the value does not save - instead, the value blanks out and validation immediately fails. While debugging, all the proper things are happening event wise up until EditModeEnding moves to EditModeEnded - this is where the internal text box in the XamTextEditor somehow becomes NULL, so nothing is really saved.
I am just checking if you got this worked out or you still require any assistance or clarification on the matter.
I created a sample project for you following your scenario and everything seems to work ok on my side. If the sample doesn’t satisfies all your needs feel free to modify it, so it reproduces your behavior and send it back to me for further investigation.
Something new that I have found, is that on a working earlier version of the software, the text box becomes null so this is normal - but the DisplayText isn't being persisted through the event change.