Thank you for your response.  

I set the data context of my window to be an object that happens to have an integer property.  I then bind the value of the editor to that integer property with respect to the data context (something like Value="{Binding Path=MyIntegerProperty}"). 

I tried using the NullText property but didn't have much success.  Does it only work for nullable ints? 

I followed your steps but again failed to reproduce this:

I set my DataContext to this and bind the XamNumericEditor to the Integer property. No exceptions.

this.DataContext = new Person();

public class Person

    {

        public string Name { get; set; }

        public int Integer { get; set; }

        public Person()

        {

            this.Name = "name";

            this.Integer = 1;

        }

    }

If you have a sample project, please attach it to your next post, or give information about your dll versions.

Just to make sure: the error that I mentioned is displayed in the Output window in visual studio when I type into the editor, is that what you were checking too?

Yes, I get this when I try to change the value, but not when I bind it initially, but I suppose this is an expected behavior. ValueType would be the property to set to avoid this, as the double value type is probably the default for this.

Alex.

Is there any way to avoid having to set value type on every instance of the XamNumericEditor (just making sure since it is a bit of extra work to do this everywhere)? 

Also, were you able to see the problem where if you clear the text in the XamNumericEditor,  your int property isn't set to 0? 

Thanks

You can create a style for the XamNumericEditor with no key, which will be automatically applied to all the XamNumericEditors like this:

<Style TargetType="{x:Type igEditors:XamNumericEditor}">
<Setter Property="ValueType" Value="{x:Type sys:Int32}"/>
</Style>

....

<igEditors:XamNumericEditor Value="{Binding Integer}" NullText="this is null text" Name="xamNumericEditor1">

...

Just to help anyone -- the above post works for null value text -- here's an example of what I've done that works for us:

                                        <igEditors:XamNumericEditor Name="txtSpeed" Width="50" EditModeStarted="Numeric_EditModeStarted"
                                                                    ToolTip="RPMs must be between 200 and 3600." NullText=""
                                                                    Text="{Binding Path=EngineTests[0].Speed}"
                                                                    Value="{Binding Path=EngineTests[0].Speed}"
                                                                    Mask="nnnn" EditModeValidationError="txtSpeed_EditModeValidationError">
                                            <igEditors:XamNumericEditor.ValueConstraint>
                                                <igEditors:ValueConstraint ValidateAsType="Integer32" MinInclusive="200" MaxInclusive="3600"></igEditors:ValueConstraint>
                                            </igEditors:XamNumericEditor.ValueConstraint>
                                        </igEditors:XamNumericEditor>

It's a pitty that xamNumericEditor doesn´t get the type of the bound property automatically. This means more work for developers each time a xamNUmericEditor is used in the form. Maybe in next release?

If you bind to Text property instead of Value, the set method of the property is triggered every time that the control gets or loses focus, or thw window is closed. If you bind to Value, the set method only is executed when the property actually changes.

I've found that if I both bind my properties to Text instead of Value and if I set Text = 0 when Text is null or empty after edit mode ends (via the event handler), then both of my problems are solved.

Thank you for all of your help with this.

I believe that has to be handled by the EditModeStarted/ing and EditModeEnded/ing events. As you have many editors, you can use the EventManager.RegisterClassHandler method do hook them up all at once, and perform this logic there (check for the value, conver value, set text if the ValueEditor has invalid value, etc..)

Alex.

Hey,

Sorry for the delayed response.  Yes, when the text is cleared, it can't parse an int so it goes to Binding.DoNothing.  My concern is that it looks like the data is cleared when it really isn't. 

If I use the control as it is intended to be used (which I assume means that I need to set ValueType), is there any built in way to prevent this clearing confusion?  I tried setting InvalidValueBehavior = "RevertValue" since I figured an empty value is invalid for an int and that it would revert the text back to what it was, but it didn't work.