since updating from v10.2 to v18.1 the DoublePositiveWithSpin doesn't work when clicking the part after the comma and trying to modify the value with arrow keys. It only works using the part before the comma. Was there some change in the API that I'm not aware of?
UltraGridColumn columnEmissivity = m_ultraGrid.DisplayLayout.Bands.Columns[iRowEmissivity];columnEmissivity.Style = Infragistics.Win.UltraWinGrid.ColumnStyle.DoublePositiveWithSpin;columnEmissivity.MaskInput = "-nn.nn";Thanks in advance
PS: I also tried using a sample I found somewhere on this website together with v19.1 which didn't change anything.
Thank you for contacting Infragistics!
I have done some looking into this matter and have some questions. What version/service release of v18.1 and v19.1 are you using? When I test this with v19.1.150 I do not reproduce the issue in most cases. I only see this when the starting value is 0.00. Do you see this behavior in any other case?
I'm using 18.1.20181.305 and 19.1.20191.82 and can confirm that your solution file works.
In my sample mentioned above with 19.1.20191.82 it still doesn't work:
Do you have any hint what might be the reason?
I ran your sample and it comes up with focus already in a grid cell with a mask. So I tried using the arrow keys and they work fine for me. Is that where the problem occurs for you? Or am I looking at the wrong cell or something?
I am using the latest internal build here. So it's possible that this was a bug in build 82 that has since been fixed. You might just want to try getting the latest service release and/or bi-weekly build and see if that fixes it.
Do the arrow keys only fail to work when the cell is initially blank? If the cell already has a value that you typed in, do the arrows work at that point?
Arrow keys after loading (left side of the comma) work fine, but when I move the carret right side of the decimal delimiter, arrow keys do not work anymore, regardless if there is a value after the comma or just the blank line.
Sorry, that's what I get for coming into the thread late. I missed that part. I can reproduce the problem with the latest version and it worked correctly in some older versions.
So the behavior definitely changed and this is something we need to look into.