These are not the only properties you can use in your Triggers , however they are common examples because they are easy to understand and easy to demonstrate.
In truth, you can watch Trigger on a Trigger DependencyProperty , but since it "fires" when the value changes (and matches the Value that you say to keep track of it), it only makes sense to change at run time, often from - due to user action (for example, focus, mouse, clicking, etc.). Only certain values ββof the actual DependencyProperties replacement in these circumstances, so not all of them make sense to use in Triggers .
Microsoft has added several standard DependencyProperties to the standard controls so you can easily create triggers based on changes. However, you can also create your own controls using your own DependencyProperties and have triggers that respond when custom DependencyProperties changes.
Keep in mind PropertyTriggers is just one Trigger flavor in WPF. There are also EventTriggers and DataTriggers and MultiTriggers . These other triggers fire depending on events or data changes or in the case of MultiTriggers values ββof several properties (or data).
Is there anything specific you are trying to do with Triggers ? This other answer gives a good explanation of what each type of trigger does.
source share