I'm using What I assume is either a XamNumericEditor or a XamMaskedEditor in a XamDataGrid to get an integer value and have set it up using the following code:

<igDP:Field Name="Item" Label="Item #">

<igDP:Field.Settings>

<igDP:FieldSettings LabelWidth="100" EditAsType="{x:Type sys:Int32}" CellValuePresenterStyle="{StaticResource InputCellStyle}" EditorStyle="{StaticResource InputEditorStyle}" />

</igDP:Field.Settings>

</igDP:Field>

When I select the field and enter a number (from either place on the keyboard), I get a pop-up with the message "No symbols are loaded for any call stack frame. The source code cannot be displayed." followed by an exception dialog saying that a FormatException occurred.  The exception has no message and the only information that is given is the source ("Infragistics3.Wpf.Editors.v7.2") and the stack trace ("   at Infragistics.Windows.Editors.NumberSection.d()").  The exception occurs sometime between the PreviewKeyDown event and the KeyDown event.

Once the exception ooccurs, the program still runs, but, most times, the number that was pressed is not entered.  If, by chance, the number does make it into the control's display after the exception occurs, then any subsequent keypresses are accepted (e.g. the '2' in '12' goes in fine if you can get the '1' in).  If you delete or otherwise remove all of the entered numbers so that the field is empty again, the exceptions start to show up again.

I've tried setting the EditAsType to Double, but that gets me another set of exceptions that occur when I try to delete the value (among other things) as follows:

A first chance exception of type 'System.InvalidCastException' occurred in InventoryManagement.exe

A first chance exception of type 'System.Reflection.TargetInvocationException' occurred in mscorlib.dll

A first chance exception of type 'System.Reflection.TargetInvocationException' occurred in mscorlib.dll

A first chance exception of type 'System.Reflection.TargetInvocationException' occurred in PresentationFramework.dll

I realize that this kind of problem takes a long time to track down and fix, but it's greatly impeding my work, so if somebody could give a work-around that is fast to implement, I'd really appreciate it.  I'd also like to know if there's some other place I should be posting this.  Thanks in advance.