Assembly: System.Windows (in System.Windows.dll)
XMLNS for XAML: Not mapped to an xmlns.
<Thickness ...>uniform</Thickness> - or - <Thickness ...>left&right,top&bottom</Thickness> - or - <Thickness ...>left,top,right,bottom</Thickness>
<object property="uniform"/> - or - <object property="left&right,top&bottom"/> - or - <object property="left,top,right,bottom" ... />
In the XAML syntaxes shown above, you can also use one or more spaces as the delimiter between values, rather than a comma.
See Remarks for additional information on value constraints that apply both to XAML and to code.
Thetype exposes the following members.
|Bottom||Gets or sets the width, in logical pixels, of the lower side of the bounding rectangle.|
|Left||Gets or sets the width, in logical pixels, of the left side of the bounding rectangle.|
|Right||Gets or sets the width, in logical pixels, of the right side of the bounding rectangle.|
|Top||Gets or sets the width, in logical pixels, of the upper side of the bounding rectangle.|
|Equals(Object)||Compares this structure to another Object for equality. (Overrides ValueType.Equals(Object).)|
|Equals(Thickness)||Compares this structure to another structure for equality.|
|Finalize||Allows an object to try to free resources and perform other cleanup operations before the Object is reclaimed by garbage collection. (Inherited from Object.)|
|GetHashCode||Returns the hash code of the structure. (Overrides ValueType.GetHashCode().)|
|GetType||Gets the Type of the current instance. (Inherited from Object.)|
|MemberwiseClone||Creates a shallow copy of the current Object. (Inherited from Object.)|
|ToString||Returns the string representation of the structure. (Overrides ValueType.ToString().)|
All property values of a must be greater than 0. The programmatic upper limit for values is not PositiveInfinity, it is a lower number (approximately 1,000,000) that is enforced by the Windows Phone native code.
Although the type of the property values of a is Double, you generally should use integer values.
In XAML, you can specify values in several ways. If you specify four Double values, these represent the Left, Top, Right and Bottom sides, respectively, of the bounding rectangle. if you specify two values, these represent the Left, Top values, and also applies the same values to Right and Bottom such that the resulting is isometric horizontally and isometric vertically. You can also supply a single value, which applies a uniform value to all four sides of the bounding rectangle. Note that although a format that specifies three values does not cause a parser error, the first value is used for both the left and right value, and any third value is ignored. This is why a three-value usage is not shown (it is really the two-value form being interpreted.) Values assigned from code do not have any behavior that can extrapolate values. If you set the value for Left, you do not automatically establish the same value for Right. All properties must be set discretely in code, although the Thickness(Double) constructor provides a way to set an initial uniform value.
Properties of do not support an attribute syntax in XAML for Windows Phone. In XAML you should always specify -type properties through one of the following usages:
The XAML attribute usage, which infers properties that use the type and uses a type converter to process the attribute string into the specific values for the .
A property element usage, containing a object element. For that object element, set the properties using initialization text, as shown in the XAML Object Element Usage.
If you specify a for use as a resource, use the object element usage and set the properties using initialization text.