I have two IntegerUpDown controls on a window. They are each bound to properties on the code behind cs file. Those are interacting with a class of R & D testing property values, which gets serialized and deserialized as a means of save and load.
Here's the problem, one works and is interactive with its bound property and one isn't. I know it has to be something I'm overlooking but I sure can't see it.
If you change the value on the IntegerUpDown for IterationGap and the value propagates through all the files/classes. It saves/load correctly; restoring when you relaunch the application. IterationCount does NOT restore at launch. It does not change with the GUI.
But if you change values on the IterationCount IntegerUpDown control there is no stop at the breakpoints for those properties.
So it seems it would have to be a mistake/difference in the binding on the WPF window XAML, right? Seems like a "duh" situation. But they look the same to me:
If one was wrong, then the IDE would bring it to my attention, so it *must* be doing the binding, right?
This is the serialed RandDobj with the values
Does anyone see a difference between how these two controls and corresponding properties are coded/implemented that would cause this difference in behavior? Or have any other clue what would cause it?