Hi,
I’m using XamNumericEditor (NetAdvantage 2010.2 WPF). I noticed the following behavior in an editor configured for negative and positive number: if a selection was made in the editor and user starts typing with - (minus), the editor doesn’t allow enter –. This only happens when a selection is made.
Scenario: XAML: <Grid><igEditors:XamNumericEditor HorizontalAlignment="Left" Margin="12,12,0,273" Name="xamNumericEditor1" Width="244" Mask="-nnn" Value="0" ValueType="{x:Type System:Int32}"/></Grid>
1. Open the window. The editor has value of 0.2. Select “0”3. Press -.
Sound of invalid character is played. Expected behavior: – (minus) character is displayed and the editor remains in the editor mode.If you select the entire string in the editor (with all padding characters), the control behaves normally and I can start editing with –.
Thanks,Sergey.
Hello,
We have shipped out a new service release where your issue is resolved. I'd be glad to find out if you had tested it out and if it had met your requirements.
You can download the Service Releases by logging to our web site and going to Account \My Keys and Downloads.
Hello Anne-Lise,
I have logged this with development under ID: 95408 and I have also created a support ticket on your behalf: CAS-75825-CDY36S and have linked the development issue to it, so that you can get automatically updated, when a Service Release containing the fix is available for download. You can get the new version from our website’s “My IG”, “My Keys & Downloads” tags: https://ko.infragistics.com/Membership/Default.aspx?panel=Downloads#Downloads
You can also monitor the support ticket’s progress through the “My Support Activity” tag: https://ko.infragistics.com/Membership/MySupport.aspx
I have the 11.1 version and exactly the same problem.
Anne-Lise
Hello Sergey,
It has been a while since you have made your post, in case you still need support I will be glad to assist you further. I suppose the other community members can benefit from this answer as well. I have been looking through your post and I can say that in our latest service releases for versions 10.3 and 11.1 your issue is resolved. Because we no longer provide fixes for version 10.2 I suggest you purchase 11.1 or wait till we ship 11.2 by the first week of November.
Feel free to write me if you have further questions.