Hi,
If the mask in only can input numbers and PromptChar is null. When try to using Microsoft Chinese input methods to type "123" in control editor, the control will showing inverse text in editor.
I'm using IG 15.1 to found this. I must say our company testers are genius. :)
Xaml codes:
Input method:
See the checked input methods as below.
Hello Brandon and thank you for posting!
I have put together a sample application trying to reproduce the behavior you have shared and it seems that I am missing something in the scenario. Would you please have a look at the attached sample project and modify it to illustrate the issue? I have tested this with version 15.1.20151.2188 and with the Chinese language settings that you have provided.
Hi Maria,
It's my mistake. I forgot upload the xaml codes. You need add a mask which is "nnnn" to reproduce this issue.
<igDP:XamMaskedInput Mask="nnnnn" PromptChar="" Text="{Binding Text,UpdateSourceTrigger=PropertyChanged}"/>
Hello Maria, thanks a lot for the reply. Your suggestion helped to solve the problem. Currently we had set empty string ("") as PromptChar. Will the behaviour be different (other than it fixes the input method problem) with a space as PromptChar?
First tests didn't show anything obvious but I just wanted to make sure.
Hello,The issue with the incorrect order of the entered digits when the PromptChar is an empty string and mask is set to “nnnnn” was fixed. The fix is available in the latest service release versions - 16.1.20161.2174 and 16.2.20162.2045 and could be downloaded from My Keys & Downloads section.You can use an empty space as PromptChar to force the digits to be displayed in the correct order in versions before the fix was applied.
<ig:XamMaskedInput HorizontalAlignment="Left" VerticalAlignment="Top" Width="150" Mask="nnnnn" PromptChar=" "/>
Hello - someone there? We need to at least know whether this is fixed in the current version of Infragistics WPF.
Having a workaround on client side (other than not using this input method) would be great.
Hello Maria - we have the same problem (with an earlier version). Two questions:
- is there a workaround in application code to avoid this issue?
- is the problem already fixed in a newer version?
Hello Brandon,
Thank you for the additional details. They helped me reproduce the issue. I have logged this behavior in our tracking system with ID 211289 and the following case was created for you: CAS-167640-T5Y7Y5. The next step will be for a developer to review my investigation and confirm my findings or to offer a fix, or other resolution.