I have a grid where each column has a different numeric editor control set for the column with different min/max values. This is all working as expected.
My problem is that I have (for example) a column with a numeric editor mask input set to "n.nn" and with a max value of 4. If I tab to this field and enter a value in the 1s place that is greater then the max value the editor places the value to in the first decimal place. So, if I try to enter
6.__ what I get is _.6__
While it is true that the value I'm entering is greater than the max allowed what I was expecting is that the editor would either not accept the value in that position or would produce some form of validation error so that I could tell the user that the value is out of range. Placing the value as it does is currently causing lots of value data entry errors.
Am I missing something here? The code I have is like the following
UltraNumericEditor normalNumericEditor = new UltraNumericEditor();normalNumericEditor.NumericType = NumericType.Double;normalNumericEditor.FormatString = "F";if (question.MaxValue < 10.0) normalNumericEditor.MaskInput = "n" + numberFormatString;else if (question.MaxValue < 100.0) normalNumericEditor.MaskInput = "nn" + numberFormatString;else normalNumericEditor.MaskInput = "nnn" + numberFormatString;normalNumericEditor.Appearance.TextHAlign = HAlign.Center;gridColumn.Style = Infragistics.Win.UltraWinGrid.ColumnStyle.Double;gridColumn.Format = normalNumericEditor.FormatString;gridColumn.MaskInput = normalNumericEditor.MaskInput;gridColumn.EditorControl = normalNumericEditor;
Is there something I'm not doing right here?
Neil
Thanks for the reply. What I ended up doing was to make the min/max 10x bigger and set the input format to only take the actual value positions exptected (e.g. if the max value was 5 I'd set the the max for the cell to 10 and then set an input mask of n.nn) I then handle the actual validation and notification elsewhere.
On developer support..I've kind of given up on the route. I just get the standard ... provide me with a simple example response ... and I usually don't have the time in my schedule to try to do that...so don't submit things there any more (sorry).
I believe that this is expected behavior since the mask sees that the current section does not allow a value in this place, so it moves it over into the next section that does allow it; if none of the sections allowed that number, I would think that at that point pressing the key would do nothing. I don't think that there is any way to override this behavior, though you could contact Developer Support to see if they have any additional insight.
-Matt