new XML Element are created for Example for Binding, wich are not yet in the XML Tree, when XamlTypeResolverProvider is used, but
the ParentObject Property is set!
With this Method you find the correct Namespace through the Tree
When not, sometimes when you Select Controls you move them Around even if you don't want to do this, because the Scrollviewer Scrolls
while Mouse Button is pressed!
Show a Info Text in the Container so that the User knows this!
=> same Behavior like in VS, because when you Enter automaticaly you can not move Contrls on Top of a Container with the Mouse
Changed the Filter TextBox to a Clearable Text Box
Made Icons for Switching between Events and Properties View
Mad already icons for different property Group Modes (Popular, PropertyGroups and All) but these need to be implemented (Icons now commented out!)
- 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
jkuehner
Siegfried Pammer
jogibear9988
Matt Ward