- Fix Problems with nested TextBlocks (Text was removed when it was set)
- Fix that not every ContentControl can have a String as Content (for Example Zoom Control in Extended WPF Toolkit)
src\AddIns\DisplayBindings\WpfDesign\WpfDesign.XamlDom\Project\XamlProperty.cs
Original author: Tobias Gummesson
------------------------------------------------------------------------------------------------------------------------
The previous solution regarding XAML names expected all properties of type string named Name to represent a name in XAML namescope, and this caused trouble with types with a property named Name that did not represent a XAML name. In this case the value of the property tried to be registered as name to the namescope and this caused either the value to be occupied as name, or threw an exception if name already was taken or the value consisted of characters forbidden in XAML names causing the value to not be set at all.
To solve this the value of a Name property is only registered to namescope if the property represents a XAML name (defined by RuntimeNamePropertyAttribute).
Also added a Name property to XamlObject that always sets the name to x:Name attribute, but gets it from either x:Name or the property that represents the XAML name if it exists (both are valid places for name registration).
Fixed a bug in XamlParser where x:Name value was not registered in its namescope.
All other changes (for example changes in PropertyGrid/XamlDesignItem) was to support the Name fixes described above.
- Aviability to Enable/Disable Raster and Snapline Placement from the Zoom Control (like in VS2012)
- Fix in Snapline Placement that you can also Position to 0!
This works, because before the Action was AddItem, and then the DefaultPlacementBehavior tries to set the position!
This should not be done by paste from Clipboard
This is necessary after the fix in commit 295f62532f.
Before that commit the ReportErrors was semi-optional; When loading was successful ReportErrors was never called (ReportErrors optional), but when document failed to be created a NullReferenceException was thrown because ReportErrors did not have a delegate.
See also commit 006558f253, that throws a more friendly exception than NullReferenceException when document fails to load.
Fixing this in CreatePropertyElement method also fixed another bug for AddChildNodeToProperty method that was fixed earlier in InsertNodeInCollection method with commit comment as follows:
"Its WPF standard to use parent type name as prefix before the dot when declaring a property as XAML element, and NOT the name of the type that declares the property."
jkuehner
Siegfried Pammer
jogibear9988
Matt Ward
Tobias Gummesson