Currently the NumberEditor in PropertyGrid tries to assign null to the underlying NumericUpDown control for ambiguous values. This results in a binding exception and the value "0.0" is being rendered in the PropertyGrid.
I changed the Value property of NumericUpDown to a nullable double. When null is assigned, the control renderes blank.
I certify that I own, and have sufficient rights to contribute, all source code and related material intended to be compiled or integrated with the source code for the WPF Designer open source product (the "Contribution"). My Contribution is licensed under the MIT License.
Currently the NumberEditor in PropertyGrid tries to assign null to the underlying NumericUpDown control for ambiguous values. This results in a binding exception and the value "0.0" is being rendered in the PropertyGrid.
I changed the Value property of NumericUpDown to a nullable double. When null is assigned, the control renderes blank.
I certify that I own, and have sufficient rights to contribute, all source code and related material intended to be compiled or integrated with the source code for the WPF Designer open source product (the "Contribution"). My Contribution is licensed under the MIT License.