Binding NumericUpDown.Value to an app setting only works in one direction

[Jesse McGrew]

Using Visual Studio 2005, I've placed a few NumericUpDown controls on a
form and bound their Value properties to user-scope application
settings. The bindings seem to work fine at design time, but only work
in one direction at runtime. When I open the form, the control values
are correctly set, but changing the values does *not* update the app
settings! Closing the form and/or calling
Properties.Settings.Default.Save() doesn't help. What's the deal?

Jesse

 

[Jesse McGrew]

Using Visual Studio 2005, I've placed a few NumericUpDown controls on a
form and bound their Value properties to user-scope application
settings. The bindings seem to work fine at design time, but only work
in one direction at runtime. When I open the form, the control values
are correctly set, but changing the values does *not* update the app
settings! Closing the form and/or calling
Properties.Settings.Default.Save() doesn't help. What's the deal?

Nobody?

This seems like a glaring bug in the app setting bindings: the setting
value is copied into the control, but the only way to get the changed
value from the control back into the app setting is by copying it
manually in a ValueChanged (or FormClosing, etc.) event. The bug
doesn't seem to occur with other controls.

Jesse