mirror of
https://github.com/Stone-Red-Code/docs-desktop.git
synced 2026-09-04 09:06:04 +02:00
Content update - Dependency properties precedence (user story 1878471) (#1164)
* Add new snippet for dependency precedence article * Add article * Minor edits * Update dotnet-desktop-guide/net/wpf/properties/dependency-property-value-precedence.md Co-authored-by: Andy (Steve) De George <[email protected]> * Update dotnet-desktop-guide/net/wpf/properties/dependency-property-value-precedence.md Co-authored-by: Andy (Steve) De George <[email protected]> * Make reviewer requested changes * Revert "Add new snippet for dependency precedence article" This reverts commit 11657c18bdf9b8ed8037e689b84be643d7e7b9e7. * Fix snippet path * Remove unneeded code project files * Header edit * Update dotnet-desktop-guide/net/wpf/properties/dependency-property-value-precedence.md Co-authored-by: Andy (Steve) De George <[email protected]> * Remove VB code project * Redirects Co-authored-by: Andy (Steve) De George <[email protected]> Co-authored-by: Andy De George (adegeo) <[email protected]>
This commit is contained in:
Tris Shores
co-authored by
Andy De George
Andy De George
Andy De George
Andy De George
parent
ba341c97c3
commit
41f8a0c942
@@ -480,6 +480,14 @@
|
||||
{
|
||||
"source_path": "dotnet-desktop-guide/framework/wpf/properties/dependency-properties-overview.md",
|
||||
"redirect_url": "/dotnet/desktop/wpf/advanced/dependency-properties-overview?view=netframeworkdesktop-4.8"
|
||||
},
|
||||
{
|
||||
"source_path": "dotnet-desktop-guide/net/wpf/advanced/dependency-property-value-precedence.md",
|
||||
"redirect_url": "/dotnet/desktop/wpf/properties/dependency-property-value-precedence?view=netdesktop-5.0"
|
||||
},
|
||||
{
|
||||
"source_path": "dotnet-desktop-guide/framework/wpf/properties/dependency-property-value-precedence.md",
|
||||
"redirect_url": "/dotnet/desktop/wpf/advanced/dependency-property-value-precedence?view=netframeworkdesktop-4.8"
|
||||
}
|
||||
]
|
||||
}
|
||||
|
||||
@@ -0,0 +1,127 @@
|
||||
---
|
||||
title: "Dependency property value precedence"
|
||||
description: Learn how the precedence of different property-based inputs within the WPF property system determines the effective value of a dependency property.
|
||||
ms.date: "09/30/2021"
|
||||
helpviewer_keywords:
|
||||
- "dependency properties [WPF], classes as owners"
|
||||
- "dependency properties [WPF], metadata"
|
||||
- "classes [WPF], owners of dependency properties"
|
||||
- "metadata [WPF], dependency properties"
|
||||
---
|
||||
<!-- The acrolinx score was 92 on 10/01/2021-->
|
||||
|
||||
# Dependency property value precedence (WPF .NET)
|
||||
|
||||
The workings of the Windows Presentation Foundation (WPF) property system affect the value of a dependency property. This article explains how the precedence of different property-based inputs within the WPF property system determines the effective value of a dependency property.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
The article assumes a basic knowledge of dependency properties, and that you've read [Dependency properties overview](dependency-properties-overview.md). To follow the examples in this article, it helps if you're familiar with Extensible Application Markup Language (XAML) and know how to write WPF applications.
|
||||
|
||||
## The WPF property system
|
||||
|
||||
The WPF property system uses a variety of factors to determine the value of dependency properties, such as real-time property validation, late binding, and property change notifications for related properties. Although the order and logic used to determine dependency property values is complex, learning it can help you avoid unnecessary property settings, and also to figure out why an attempt to set a dependency property didn't result in the expected value.
|
||||
|
||||
### Dependency properties set in multiple places
|
||||
|
||||
The following XAML example shows how three different "set" operations on the button's <xref:System.Windows.Controls.Control.Background%2A> property can influence its value.
|
||||
|
||||
:::code language="xaml" source="./snippets/dependency-property-value-precedence/csharp/MainWindow.xaml" id="DependencyPropertyValuePrecedence":::
|
||||
|
||||
In the example, the `Background` property is locally set to `Red`. However, the implicit style declared in the button's scope, attempts to set the `Background` property to `Blue`. And, when the mouse is over the button, the trigger in the implicit style attempts to set the `Background` property to `Yellow`. Except for coercion and animation, a locally set property value has the highest precedence, so the button will be red—even on mouseover. But, if you remove the locally set value from the button, then it will get its `Background` value from the style. Within a style, triggers take precedence, so the button will be yellow on mouseover, and blue otherwise. The example replaces the button's default <xref:System.Windows.Controls.ControlTemplate> because the default template has a hard-coded mouseover `Background` value.
|
||||
|
||||
## Dependency property precedence list
|
||||
|
||||
The following list is the definitive order of precedence that the property system uses when assigning runtime values to dependency properties. Highest precedence is listed first.
|
||||
|
||||
1. **Property system coercion**. For more information about coercion, see [Coercion and animations](#coercion-and-animation).
|
||||
|
||||
2. **Active animations, or animations with a Hold behavior**. To have a practical effect, an animation value must have precedence over the base (unanimated) value, even if the base value was set locally. For more information, see [Coercion and animations](#coercion-and-animation).
|
||||
|
||||
3. **Local values**. You can set a local value through a "wrapper" property, which equates to setting an attribute or property element in XAML, or by a call to the <xref:System.Windows.DependencyObject.SetValue%2A> API using a property of a specific instance. A local value set through a binding or resource will have the same precedence as a value that's directly set.
|
||||
|
||||
4. **TemplatedParent template property values**. An element has a <xref:System.Windows.FrameworkElement.TemplatedParent%2A> if it was created by a template (<xref:System.Windows.Controls.ControlTemplate> or <xref:System.Windows.DataTemplate>). For more information, see [TemplatedParent](#templatedparent). Within the template specified by the `TemplatedParent`, the order of precedence is:
|
||||
|
||||
1. Triggers.
|
||||
|
||||
1. Property sets, typically through XAML attributes.
|
||||
|
||||
5. **Implicit styles**. Applies only to the <xref:System.Windows.FrameworkElement.Style%2A> property. The `Style` value is any style resource with a <xref:System.Windows.Style.TargetType%2A> value that matches the element type. The style resource must exist within the page or application. Lookup for an implicit style resource doesn't extend to styles resources in Themes.
|
||||
|
||||
6. **Style triggers**. A style trigger is a trigger within an explicit or implicit style. The style must exist within the page or application. Triggers in default styles have a lower precedence.
|
||||
|
||||
7. **Template triggers**. A template trigger is a trigger from a directly applied template, or from a template within a style. The style must exist within the page or application.
|
||||
|
||||
8. **Style setter values**. A style setter value is a value applied by a <xref:System.Windows.Setter> within a style. The style must exist within the page or application.
|
||||
|
||||
9. **Default styles**, also known as **theme styles**. For more information, see [Default (Theme) styles](#default-theme-styles). Within a default style, the order of precedence is:
|
||||
|
||||
1. Active triggers.
|
||||
|
||||
1. Setters.
|
||||
|
||||
10. **Inheritance**. Some dependency properties of a child element inherit their value from the parent element. So, it might not be necessary to set property values on every element throughout the application. For more information, see [Property value inheritance](/dotnet/desktop/wpf/advanced/property-value-inheritance?view=netframeworkdesktop-4.8&preserve-view=true).
|
||||
|
||||
11. **Default value from dependency property metadata** A dependency property can have a default value set during property system registration of that property. Derived classes that inherit a dependency property can override dependency property metadata (including the default value) on a per-type basis. For more information, see [Dependency property metadata](/dotnet/desktop/wpf/advanced/dependency-property-metadata?view=netframeworkdesktop-4.8&preserve-view=true). For an inherited property, the default value of a parent element takes precedence over the default value of a child element. So, if an inheritable property isn't set, the default value of the root or parent is used instead of the default value of the child element.
|
||||
|
||||
## TemplatedParent
|
||||
|
||||
<xref:System.Windows.FrameworkElement.TemplatedParent%2A> precedence doesn't apply to properties of elements that are declared directly in standard application markup. The `TemplatedParent` concept exists only for child items within a visual tree that come into existence through the application of a template. When the property system searches the template specified by the `TemplatedParent` for the property values of an element, it's searching the template that created the element. The property values from the `TemplatedParent` template generally act as if they were locally set values on the element, but with lesser precedence than actual local values because templates are potentially shared. For more information, see <xref:System.Windows.FrameworkElement.TemplatedParent%2A>.
|
||||
|
||||
## The Style property
|
||||
|
||||
The same order of precedence applies to all dependency properties, except the <xref:System.Windows.FrameworkElement.Style%2A> property. The `Style` property is unique in that it cannot itself be styled. Coercing or animating the `Style` property isn't recommended (and animating the `Style` property would require a custom animation class). As a result, not all precedence items apply. There are only three ways to set the `Style` property:
|
||||
|
||||
- **Explicit style.** The `Style` property of an element is set directly. The `Style` property value acts as if it were a local value and has the same precedence as item 3 in the [precedence list](#dependency-property-precedence-list). In most scenarios, explicit styles aren't defined inline and instead are explicitly referenced as a resource, for example `Style="{StaticResource myResourceKey}"`.
|
||||
|
||||
- **Implicit style.** The `Style` property of an element isn't set directly. Instead, a style gets applied when it exists at some level within the page or application, and has a resource key that matches the type of element that the style applies to, for example `<Style TargetType="x:Type Button">`. The type must match exactly, for example `<Style TargetType="x:Type Button">` won't get applied to `MyButton` type even if `MyButton` is derived from `Button`. The `Style` property value has the same precedence as item 5 in the [precedence list](#dependency-property-precedence-list). An implicit style value can be detected by calling the <xref:System.Windows.DependencyPropertyHelper.GetValueSource%2A?displayProperty=nameWithType> method, passing in the `Style` property, and checking for `ImplicitStyleReference` in the results.
|
||||
|
||||
- **Default style**, also known as **theme style**. The `Style` property of an element isn't set directly. Instead, it comes from runtime theme evaluation by the WPF presentation engine. Before runtime, the `Style` property value is `null`. The `Style` property value has the same precedence as item 9 in the [precedence list](#dependency-property-precedence-list).
|
||||
|
||||
## Default (Theme) styles
|
||||
|
||||
Every control that ships with WPF has a default style that can vary by theme, which is why the default style is sometimes referred to as a *theme style*.
|
||||
|
||||
The <xref:System.Windows.Controls.ControlTemplate> is an important item within the default style for a control. `ControlTemplate` is a setter value for the style's <xref:System.Windows.Controls.Control.Template%2A> property. If default styles didn't contain a template, a control without a custom template as part of a custom style would have no visual appearance. Not only does a template define the visual appearance of a control, it also defines the connections between properties in the visual tree of the template and the corresponding control class. Each control exposes a set of properties that can influence the visual appearance of the control without replacing the template. For example, consider the default visual appearance of a <xref:System.Windows.Controls.Primitives.Thumb> control, which is a <xref:System.Windows.Controls.Primitives.ScrollBar> component.
|
||||
|
||||
A <xref:System.Windows.Controls.Primitives.Thumb> control has certain customizable properties. The default template of a `Thumb` control creates a basic structure, or visual tree, with several nested <xref:System.Windows.Controls.Border> components to create a beveled look. Within the template, properties that are intended to be customizable by the `Thumb` class are exposed through [TemplateBinding](/dotnet/desktop/wpf/advanced/templatebinding-markup-extension?view=netframeworkdesktop-4.8&preserve-view=true). The default template for the `Thumb` control has various border properties that share a template binding with properties such as <xref:System.Windows.Controls.Border.Background%2A> or <xref:System.Windows.Controls.Border.BorderThickness%2A>. But, where values for properties or visual arrangements are hard-coded in the template, or are bound to values that come directly from the theme, you can only change those values by replacing the entire template. Generally, if a property comes from a templated parent and isn't exposed by a `TemplateBinding`, then the property value cannot be changed by styles because there's no convenient way to target it. But, that property might still be influenced by property value inheritance in the applied template, or by a default value.
|
||||
|
||||
Default styles specify a <xref:System.Windows.Style.TargetType%2A> in their definitions. Runtime theme evaluation matches the `TargetType` of a default style to the <xref:System.Windows.FrameworkElement.DefaultStyleKey%2A> property of a control. In contrast, the lookup behavior for implicit styles uses the actual type of the control. The value of `DefaultStyleKey` is inherited by derived classes, so derived elements that might otherwise have no associated style get a default visual appearance. For example, if you derive `MyButton` from <xref:System.Windows.Controls.Button>, `MyButton` will inherit the default template of `Button`. Derived classes can override the default value of `DefaultStyleKey` in dependency property metadata. So, if you want a different visual representation for `MyButton`, you can override the dependency property metadata for `DefaultStyleKey` on `MyButton`, and then define the relevant default style including a template, that you'll package with your `MyButton` control. For more information, see [Control authoring overview](/dotnet/desktop/wpf/controls/control-authoring-overview?view=netframeworkdesktop-4.8&preserve-view=true).
|
||||
|
||||
## Dynamic resource
|
||||
|
||||
[Dynamic resource](/dotnet/desktop/wpf/advanced/dynamicresource-markup-extension?view=netframeworkdesktop-4.8&preserve-view=true) references and binding operations have the precedence of the location at which they're set. For example, a dynamic resource applied to a local value has the same precedence as item 3 in the [precedence list](#dependency-property-precedence-list). As another example, a dynamic resource binding applied to a property setter within a default style has the same precedence as item 9 in the [precedence list](#dependency-property-precedence-list). Because dynamic resource references and binding must get values from the runtime state of the application, the process for determining property value precedence for any given property extends into runtime.
|
||||
|
||||
Dynamic resource references aren't technically part of the property system, and have their own lookup order that interacts with the [precedence list](#dependency-property-precedence-list). Essentially, the precedence of dynamic resource references is: element to page root, application, theme, and then system. For more information, see [XAML Resources](/dotnet/desktop/wpf/systems/xaml-resources-overview).
|
||||
|
||||
Although dynamic resource references and bindings have the precedence of the location at which they're set, the value is deferred. One consequence of this is that if you set a dynamic resource or binding to a local value, any change to the local value entirely replaces the dynamic resource or binding. Even if you call the <xref:System.Windows.DependencyObject.ClearValue%2A> method to clear the locally set value, the dynamic resource or binding won't be restored. In fact, if you call `ClearValue` on a property that has a dynamic resource or binding (with no literal local value), the dynamic resource or binding will be cleared.
|
||||
|
||||
## SetCurrentValue
|
||||
|
||||
The <xref:System.Windows.DependencyObject.SetCurrentValue%2A> method is another way to set a property, but it's not in the [precedence list](#dependency-property-precedence-list). `SetCurrentValue` lets you change the value of a property without overwriting the source of a previous value. For example, if a property is set by a trigger, and then you assign another value using `SetCurrentValue`, the next trigger action will set the property back to the trigger value. You can use `SetCurrentValue` whenever you want to set a property value without giving that value the precedence level of a local value. Similarly, you can use `SetCurrentValue` to change the value of a property without overwriting a binding.
|
||||
|
||||
## Coercion and animation
|
||||
|
||||
Coercion and animation both act on a *base value*. The *base value* is the dependency property value with the highest precedence, determined by evaluating upwards through the [precedence list](#dependency-property-precedence-list) until item 2 is reached.
|
||||
|
||||
If an animation doesn't specify both <xref:System.Windows.Media.Animation.DoubleAnimation.From> and <xref:System.Windows.Media.Animation.DoubleAnimation.To> property values for certain behaviors, or if the animation deliberately reverts to the base value when completed, then the base value can affect the animated value. To see this in practice, run the [Target Values](https://github.com/Microsoft/WPF-Samples/tree/master/Animation/TargetValues) sample application. In the sample, for the rectangle height, try setting initial local values that differ from any `From` value. The sample animations start right away by using the `From` value instead of the base value. By specifying <xref:System.Windows.Media.Animation.FillBehavior.Stop> as the <xref:System.Windows.Media.Animation.FillBehavior>, on completion an animation will reset a property value to its base value. Normal precedence is used for base value determination after an animation ends.
|
||||
|
||||
Multiple animations can be applied to a single property, with each animation having a different precedence. Rather than applying the animation with the highest precedence, the WPF presentation engine might composite the animation values, depending on how the animations were defined and the type of values animated. For more information, see [Animation overview](/dotnet/desktop/wpf/graphics-multimedia/animation-overview?view=netframeworkdesktop-4.8&preserve-view=true).
|
||||
|
||||
Coercion is at the top of the [precedence list](#dependency-property-precedence-list). Even a running animation is subject to value coercion. Some existing dependency properties in WPF have built-in coercion. For custom dependency properties, you can define coercion behavior by writing a <xref:System.Windows.CoerceValueCallback> that you pass as part of metadata when you create a property. You can also override the coercion behavior of existing properties by overriding the metadata for that property in a derived class. Coercion interacts with the base value in such a way that the constraints on coercion are applied as they exist at the time, but the base value is still retained. As a result, if the constraints in coercion are later lifted, the coercion will return the closest value possible to the base value, and potentially the coercion influence on a property will cease as soon as all constraints are lifted. For more on coercion behavior, see [Dependency property callbacks and validation](/dotnet/desktop/wpf/advanced/dependency-property-callbacks-and-validation?view=netframeworkdesktop-4.8&preserve-view=true).
|
||||
|
||||
## Trigger behaviors
|
||||
|
||||
Controls often define trigger behaviors as part of their [default style](#default-theme-styles). Setting local properties on controls can potentially conflict with those triggers, preventing the triggers from responding (either visually or behaviorally) to user-driven events. A common use of a property trigger is to control state properties, such as <xref:System.Windows.Controls.Primitives.Selector.IsSelected%2A> or <xref:System.Windows.UIElement.IsEnabled%2A>. For example, by default, when a <xref:System.Windows.Controls.Button> is disabled, a theme style trigger (`IsEnabled` is `false`) sets the <xref:System.Windows.Controls.Control.Foreground%2A> value to make the `Button` appear greyed out. If you've set a local `Foreground` value, the higher precedence local property value will overrule the theme style `Foreground` value, even when the `Button` is disabled. When setting property values that override theme-level trigger behaviors for a control, be careful not to unduly interfere with the intended user experience for that control.
|
||||
|
||||
## ClearValue
|
||||
|
||||
The <xref:System.Windows.DependencyObject.ClearValue%2A> method clears any locally applied value of a dependency property for an element. But, calling `ClearValue` doesn't guarantee that the default value established in metadata during property registration is the new effective value. All other participants in the [precedence list](#dependency-property-precedence-list) are still active, and only the locally set value gets removed. For example, if you call `ClearValue` on a property that has a theme style, the theme style value will be applied as the new value, rather than the metadata-based default. If you want to set a property value to the registered metadata default value, then get the default metadata value by querying the dependency property metadata, and locally set the property value with a call to <xref:System.Windows.DependencyObject.SetValue%2A>.
|
||||
|
||||
## See also
|
||||
|
||||
- <xref:System.Windows.DependencyObject>
|
||||
- <xref:System.Windows.DependencyProperty>
|
||||
- [Dependency properties overview](dependency-properties-overview.md)
|
||||
- [Custom Dependency Properties](/dotnet/desktop/wpf/advanced/custom-dependency-properties?view=netframeworkdesktop-4.8&preserve-view=true)
|
||||
- [Dependency Property Callbacks and Validation](/dotnet/desktop/wpf/advanced/dependency-property-callbacks-and-validation?view=netframeworkdesktop-4.8&preserve-view=true)
|
||||
+9
@@ -0,0 +1,9 @@
|
||||
<Application x:Class="CodeSampleCsharp.App"
|
||||
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
|
||||
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
|
||||
xmlns:local="clr-namespace:CodeSampleCsharp"
|
||||
StartupUri="MainWindow.xaml">
|
||||
<Application.Resources>
|
||||
|
||||
</Application.Resources>
|
||||
</Application>
|
||||
+17
@@ -0,0 +1,17 @@
|
||||
using System;
|
||||
using System.Collections.Generic;
|
||||
using System.Configuration;
|
||||
using System.Data;
|
||||
using System.Linq;
|
||||
using System.Threading.Tasks;
|
||||
using System.Windows;
|
||||
|
||||
namespace CodeSampleCsharp
|
||||
{
|
||||
/// <summary>
|
||||
/// Interaction logic for App.xaml
|
||||
/// </summary>
|
||||
public partial class App : Application
|
||||
{
|
||||
}
|
||||
}
|
||||
+10
@@ -0,0 +1,10 @@
|
||||
using System.Windows;
|
||||
|
||||
[assembly: ThemeInfo(
|
||||
ResourceDictionaryLocation.None, //where theme specific resource dictionaries are located
|
||||
//(used if a resource is not found in the page,
|
||||
// or application resource dictionaries)
|
||||
ResourceDictionaryLocation.SourceAssembly //where the generic resource dictionary is located
|
||||
//(used if a resource is not found in the page,
|
||||
// app, or any theme specific resource dictionaries)
|
||||
)]
|
||||
+24
@@ -0,0 +1,24 @@
|
||||
<Project Sdk="Microsoft.NET.Sdk">
|
||||
|
||||
<PropertyGroup>
|
||||
<OutputType>WinExe</OutputType>
|
||||
<TargetFramework>net5.0-windows</TargetFramework>
|
||||
<UseWPF>true</UseWPF>
|
||||
</PropertyGroup>
|
||||
|
||||
<ItemGroup>
|
||||
<Compile Update="Properties\Resources.Designer.cs">
|
||||
<DesignTime>True</DesignTime>
|
||||
<AutoGen>True</AutoGen>
|
||||
<DependentUpon>Resources.resx</DependentUpon>
|
||||
</Compile>
|
||||
</ItemGroup>
|
||||
|
||||
<ItemGroup>
|
||||
<EmbeddedResource Update="Properties\Resources.resx">
|
||||
<Generator>ResXFileCodeGenerator</Generator>
|
||||
<LastGenOutput>Resources.Designer.cs</LastGenOutput>
|
||||
</EmbeddedResource>
|
||||
</ItemGroup>
|
||||
|
||||
</Project>
|
||||
+34
@@ -0,0 +1,34 @@
|
||||
<Window x:Class="CodeSampleCsharp.MainWindow"
|
||||
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
|
||||
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
|
||||
xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
|
||||
xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
|
||||
mc:Ignorable="d"
|
||||
Title="Dependency Property Value Precedence" Height="100" Width="300">
|
||||
<!--<DependencyPropertyValuePrecedence>-->
|
||||
<StackPanel>
|
||||
<StackPanel.Resources>
|
||||
<ControlTemplate x:Key="ButtonTemplate" TargetType="{x:Type Button}">
|
||||
<Border Background="{TemplateBinding Background}" BorderThickness="{TemplateBinding BorderThickness}"
|
||||
BorderBrush="{TemplateBinding BorderBrush}">
|
||||
<ContentPresenter HorizontalAlignment="Center" VerticalAlignment="Center" />
|
||||
</Border>
|
||||
</ControlTemplate>
|
||||
</StackPanel.Resources>
|
||||
|
||||
<Button Template="{StaticResource ButtonTemplate}" Background="Red">
|
||||
<Button.Style>
|
||||
<Style TargetType="{x:Type Button}">
|
||||
<Setter Property="Background" Value="Blue"/>
|
||||
<Style.Triggers>
|
||||
<Trigger Property="IsMouseOver" Value="True">
|
||||
<Setter Property="Background" Value="Yellow" />
|
||||
</Trigger>
|
||||
</Style.Triggers>
|
||||
</Style>
|
||||
</Button.Style>
|
||||
Which color do you expect?
|
||||
</Button>
|
||||
</StackPanel>
|
||||
<!--</DependencyPropertyValuePrecedence>-->
|
||||
</Window>
|
||||
+48
@@ -0,0 +1,48 @@
|
||||
using System.Windows;
|
||||
using System.Windows.Controls;
|
||||
|
||||
namespace CodeSampleCsharp
|
||||
{
|
||||
/// <summary>
|
||||
/// Interaction logic for MainWindow.xaml.
|
||||
/// </summary>
|
||||
public partial class MainWindow : Window
|
||||
{
|
||||
public MainWindow()
|
||||
{
|
||||
InitializeComponent();
|
||||
|
||||
// <ProceduralPropertySet>
|
||||
Button myButton = new();
|
||||
myButton.Width = 200.0;
|
||||
// </ProceduralPropertySet>
|
||||
|
||||
// <ProceduralPropertyGet>
|
||||
double whatWidth = myButton.Width;
|
||||
// </ProceduralPropertyGet>
|
||||
}
|
||||
|
||||
// <DefineDependencyProperty>
|
||||
public static readonly DependencyProperty IsSpinningProperty = DependencyProperty.Register(
|
||||
"IsSpinning", typeof(bool),
|
||||
typeof(MainWindow)
|
||||
);
|
||||
|
||||
public bool IsSpinning
|
||||
{
|
||||
get => (bool)GetValue(IsSpinningProperty);
|
||||
set => SetValue(IsSpinningProperty, value);
|
||||
}
|
||||
// </DefineDependencyProperty>
|
||||
}
|
||||
|
||||
// <OverrideMetadata>
|
||||
public class SpinnerControl : ItemsControl
|
||||
{
|
||||
static SpinnerControl() => DefaultStyleKeyProperty.OverrideMetadata(
|
||||
typeof(SpinnerControl),
|
||||
new FrameworkPropertyMetadata(typeof(SpinnerControl))
|
||||
);
|
||||
}
|
||||
// </OverrideMetadata>
|
||||
}
|
||||
+63
@@ -0,0 +1,63 @@
|
||||
//------------------------------------------------------------------------------
|
||||
// <auto-generated>
|
||||
// This code was generated by a tool.
|
||||
// Runtime Version:4.0.30319.42000
|
||||
//
|
||||
// Changes to this file may cause incorrect behavior and will be lost if
|
||||
// the code is regenerated.
|
||||
// </auto-generated>
|
||||
//------------------------------------------------------------------------------
|
||||
|
||||
namespace CodeSampleCsharp.Properties {
|
||||
using System;
|
||||
|
||||
|
||||
/// <summary>
|
||||
/// A strongly-typed resource class, for looking up localized strings, etc.
|
||||
/// </summary>
|
||||
// This class was auto-generated by the StronglyTypedResourceBuilder
|
||||
// class via a tool like ResGen or Visual Studio.
|
||||
// To add or remove a member, edit your .ResX file then rerun ResGen
|
||||
// with the /str option, or rebuild your VS project.
|
||||
[global::System.CodeDom.Compiler.GeneratedCodeAttribute("System.Resources.Tools.StronglyTypedResourceBuilder", "16.0.0.0")]
|
||||
[global::System.Diagnostics.DebuggerNonUserCodeAttribute()]
|
||||
[global::System.Runtime.CompilerServices.CompilerGeneratedAttribute()]
|
||||
internal class Resources {
|
||||
|
||||
private static global::System.Resources.ResourceManager resourceMan;
|
||||
|
||||
private static global::System.Globalization.CultureInfo resourceCulture;
|
||||
|
||||
[global::System.Diagnostics.CodeAnalysis.SuppressMessageAttribute("Microsoft.Performance", "CA1811:AvoidUncalledPrivateCode")]
|
||||
internal Resources() {
|
||||
}
|
||||
|
||||
/// <summary>
|
||||
/// Returns the cached ResourceManager instance used by this class.
|
||||
/// </summary>
|
||||
[global::System.ComponentModel.EditorBrowsableAttribute(global::System.ComponentModel.EditorBrowsableState.Advanced)]
|
||||
internal static global::System.Resources.ResourceManager ResourceManager {
|
||||
get {
|
||||
if (object.ReferenceEquals(resourceMan, null)) {
|
||||
global::System.Resources.ResourceManager temp = new global::System.Resources.ResourceManager("CodeSampleCsharp.Properties.Resources", typeof(Resources).Assembly);
|
||||
resourceMan = temp;
|
||||
}
|
||||
return resourceMan;
|
||||
}
|
||||
}
|
||||
|
||||
/// <summary>
|
||||
/// Overrides the current thread's CurrentUICulture property for all
|
||||
/// resource lookups using this strongly typed resource class.
|
||||
/// </summary>
|
||||
[global::System.ComponentModel.EditorBrowsableAttribute(global::System.ComponentModel.EditorBrowsableState.Advanced)]
|
||||
internal static global::System.Globalization.CultureInfo Culture {
|
||||
get {
|
||||
return resourceCulture;
|
||||
}
|
||||
set {
|
||||
resourceCulture = value;
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
+120
@@ -0,0 +1,120 @@
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
<root>
|
||||
<!--
|
||||
Microsoft ResX Schema
|
||||
|
||||
Version 2.0
|
||||
|
||||
The primary goals of this format is to allow a simple XML format
|
||||
that is mostly human readable. The generation and parsing of the
|
||||
various data types are done through the TypeConverter classes
|
||||
associated with the data types.
|
||||
|
||||
Example:
|
||||
|
||||
... ado.net/XML headers & schema ...
|
||||
<resheader name="resmimetype">text/microsoft-resx</resheader>
|
||||
<resheader name="version">2.0</resheader>
|
||||
<resheader name="reader">System.Resources.ResXResourceReader, System.Windows.Forms, ...</resheader>
|
||||
<resheader name="writer">System.Resources.ResXResourceWriter, System.Windows.Forms, ...</resheader>
|
||||
<data name="Name1"><value>this is my long string</value><comment>this is a comment</comment></data>
|
||||
<data name="Color1" type="System.Drawing.Color, System.Drawing">Blue</data>
|
||||
<data name="Bitmap1" mimetype="application/x-microsoft.net.object.binary.base64">
|
||||
<value>[base64 mime encoded serialized .NET Framework object]</value>
|
||||
</data>
|
||||
<data name="Icon1" type="System.Drawing.Icon, System.Drawing" mimetype="application/x-microsoft.net.object.bytearray.base64">
|
||||
<value>[base64 mime encoded string representing a byte array form of the .NET Framework object]</value>
|
||||
<comment>This is a comment</comment>
|
||||
</data>
|
||||
|
||||
There are any number of "resheader" rows that contain simple
|
||||
name/value pairs.
|
||||
|
||||
Each data row contains a name, and value. The row also contains a
|
||||
type or mimetype. Type corresponds to a .NET class that support
|
||||
text/value conversion through the TypeConverter architecture.
|
||||
Classes that don't support this are serialized and stored with the
|
||||
mimetype set.
|
||||
|
||||
The mimetype is used for serialized objects, and tells the
|
||||
ResXResourceReader how to depersist the object. This is currently not
|
||||
extensible. For a given mimetype the value must be set accordingly:
|
||||
|
||||
Note - application/x-microsoft.net.object.binary.base64 is the format
|
||||
that the ResXResourceWriter will generate, however the reader can
|
||||
read any of the formats listed below.
|
||||
|
||||
mimetype: application/x-microsoft.net.object.binary.base64
|
||||
value : The object must be serialized with
|
||||
: System.Runtime.Serialization.Formatters.Binary.BinaryFormatter
|
||||
: and then encoded with base64 encoding.
|
||||
|
||||
mimetype: application/x-microsoft.net.object.soap.base64
|
||||
value : The object must be serialized with
|
||||
: System.Runtime.Serialization.Formatters.Soap.SoapFormatter
|
||||
: and then encoded with base64 encoding.
|
||||
|
||||
mimetype: application/x-microsoft.net.object.bytearray.base64
|
||||
value : The object must be serialized into a byte array
|
||||
: using a System.ComponentModel.TypeConverter
|
||||
: and then encoded with base64 encoding.
|
||||
-->
|
||||
<xsd:schema id="root" xmlns="" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
|
||||
<xsd:import namespace="http://www.w3.org/XML/1998/namespace" />
|
||||
<xsd:element name="root" msdata:IsDataSet="true">
|
||||
<xsd:complexType>
|
||||
<xsd:choice maxOccurs="unbounded">
|
||||
<xsd:element name="metadata">
|
||||
<xsd:complexType>
|
||||
<xsd:sequence>
|
||||
<xsd:element name="value" type="xsd:string" minOccurs="0" />
|
||||
</xsd:sequence>
|
||||
<xsd:attribute name="name" use="required" type="xsd:string" />
|
||||
<xsd:attribute name="type" type="xsd:string" />
|
||||
<xsd:attribute name="mimetype" type="xsd:string" />
|
||||
<xsd:attribute ref="xml:space" />
|
||||
</xsd:complexType>
|
||||
</xsd:element>
|
||||
<xsd:element name="assembly">
|
||||
<xsd:complexType>
|
||||
<xsd:attribute name="alias" type="xsd:string" />
|
||||
<xsd:attribute name="name" type="xsd:string" />
|
||||
</xsd:complexType>
|
||||
</xsd:element>
|
||||
<xsd:element name="data">
|
||||
<xsd:complexType>
|
||||
<xsd:sequence>
|
||||
<xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
|
||||
<xsd:element name="comment" type="xsd:string" minOccurs="0" msdata:Ordinal="2" />
|
||||
</xsd:sequence>
|
||||
<xsd:attribute name="name" type="xsd:string" use="required" msdata:Ordinal="1" />
|
||||
<xsd:attribute name="type" type="xsd:string" msdata:Ordinal="3" />
|
||||
<xsd:attribute name="mimetype" type="xsd:string" msdata:Ordinal="4" />
|
||||
<xsd:attribute ref="xml:space" />
|
||||
</xsd:complexType>
|
||||
</xsd:element>
|
||||
<xsd:element name="resheader">
|
||||
<xsd:complexType>
|
||||
<xsd:sequence>
|
||||
<xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
|
||||
</xsd:sequence>
|
||||
<xsd:attribute name="name" type="xsd:string" use="required" />
|
||||
</xsd:complexType>
|
||||
</xsd:element>
|
||||
</xsd:choice>
|
||||
</xsd:complexType>
|
||||
</xsd:element>
|
||||
</xsd:schema>
|
||||
<resheader name="resmimetype">
|
||||
<value>text/microsoft-resx</value>
|
||||
</resheader>
|
||||
<resheader name="version">
|
||||
<value>2.0</value>
|
||||
</resheader>
|
||||
<resheader name="reader">
|
||||
<value>System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
|
||||
</resheader>
|
||||
<resheader name="writer">
|
||||
<value>System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
|
||||
</resheader>
|
||||
</root>
|
||||
@@ -82,6 +82,8 @@ items:
|
||||
items:
|
||||
- name: Dependency properties
|
||||
href: properties/dependency-properties-overview.md
|
||||
- name: Dependency property value precedence
|
||||
href: properties/dependency-property-value-precedence.md
|
||||
- name: Resources
|
||||
items:
|
||||
- name: Overview
|
||||
|
||||
@@ -324,6 +324,11 @@
|
||||
"SourceUrl": "/dotnet/desktop/wpf/advanced/dependency-properties-overview?view=netframeworkdesktop-4.8",
|
||||
"TargetUrl": "/dotnet/desktop/wpf/properties/dependency-properties-overview?view=netdesktop-5.0"
|
||||
},
|
||||
{
|
||||
"Redirect": "TwoWay",
|
||||
"SourceUrl": "/dotnet/desktop/wpf/advanced/dependency-property-value-precedence?view=netframeworkdesktop-4.8",
|
||||
"TargetUrl": "/dotnet/desktop/wpf/properties/dependency-property-value-precedence?view=netdesktop-5.0"
|
||||
},
|
||||
|
||||
// Systems - XAML
|
||||
{
|
||||
|
||||
Reference in New Issue
Block a user