I am using a Mindscape IntegerUpDown control in a VMMV application. The first time the view model is loaded, the IntegerUpDown control works as expected. After a sequence where the view model is replaced with another instance of the same view model, the control no longer works. All of the other controls used work as expected. When the IntegerUpDown is replaced with a Mindscape NumericText box, the text box works as expected.

Problem behavior: up and down arrows have no effect. I can type in a value (within range), but instead of the expected reaction of going into the "Binding" property once, it enters 4 times. Each time, it flips the new value. For clarity, let us call the binding property MyNumber, min=1, max=9.

Mindscape.WpfElements Runtime Version = v2.0.50727, Version 6.0.2837.23219

private int mMyNumber;
public int MyNumber;
{
   get { return mMyNumber; }
   set
   {
      if (mMyNumber == value) return;
      mMyNumber = value;
      ...
   }
}

On original view model instance, pressing up arrow, down arrow or typing a valid digit causes the MyNumber property to be entered once, code works as expected. On the second view model instance, the only action that will cause this code to fire is typing in the IntegerUpDown control. Let's say the initial value was 1 and I type 2. This property set code is fired 4 times from this single key press, with the numbers:

1: mMyNumber = 1, value = 2

2: mMyNumber = 2, value = 1

3: mMyNumber = 1, value = 2

4: mMyNumber = 2, value = 1

The net effect is it does not seem to the user that the control works at all. Any ideas?

Hello

I have followed your description, but was unable to reproduce this problem. After switching view models, the control still continues to function correctly. Could you please send a simple project demonstrating this issue.

-Jason Fauchelle