Content update - Framework property metadata (user story 1878471) (#1223)

* Add article, snippets, toc, and redirects

* Minor edits

* Make reviewer requested changes

* Section header edit

Co-authored-by: Andy (Steve) De George <[email protected]>
This commit is contained in:
Tris Shores
2021-12-07 23:20:09 +00:00
committed by GitHub
co-authored by Andy De George
parent 048ceebd5d
commit 3bac863f43
5 changed files with 94 additions and 1 deletions
@@ -75,7 +75,7 @@ Since most existing dependency properties aren't virtual properties, their inher
- For a <xref:System.Windows.PropertyMetadata.DefaultValue%2A>, the new value will replace the existing default value. If you don't specify a `DefaultValue` in the override metadata, the value comes from the nearest ancestor that specified `DefaultValue` in metadata.
- For a <xref:System.Windows.PropertyMetadata.PropertyChangedCallback%2A>, the default merge logic stores all `PropertyChangedCallback` values in a table, and all are invoked on a property change. The callback order is determined by class depth, where the callback registered by the base class in the hierarchy runs first.
- For a <xref:System.Windows.PropertyMetadata.PropertyChangedCallback%2A>, the default merge logic stores all `PropertyChangedCallback` values in a table, and all are invoked on a property change. The callback order is determined by class depth, where a callback registered by the base class in the hierarchy would run first.
- For a <xref:System.Windows.PropertyMetadata.CoerceValueCallback%2A>, the new value will replace the existing `CoerceValueCallback` value. If you don't specify a `CoerceValueCallback` in the override metadata, the value comes from the nearest ancestor that specified `CoerceValueCallback` in metadata.