While most TA properties get their values directly from single native properties of
their associated controls, there are some TA properties whose values are calculated, often from
two or more native properties, or from other controls. We'll examine a few examples.
Not all TA
obtain their values directly from a single native property
. In some cases, there is a
many-to-one mapping from native to TA properties. For example, the state
property of a WPF radio button takes its value from up to five different native properties:
, and IsChecked
. (Note also that the mapping
doesn't merely copy the True
values of each property.
Instead, it derives the individual values from the combination of both the nature and value of
each native property. Hence, for example, with native property IsEnabled
, the term enabled
is included in the value of
Some secondary properties are more
complex in terms of how their values are arrived at. In some cases their values are
calculated, and in some cases those values are dependent on their host controls' physical
positions, or even on the existence or values of neighboring controls.
Some of the more important secondary properties are examined