Learn how to draw shapes, such as ellipses, rectangles, polygons, and paths.
The Path class is the way to visualize a fairly complex vector-based drawing language in a XAML UI; for example, you can draw Bezier curves.
Important APIs: Path манежи пренатал, Windows.UI.Xaml.Shapes namespace, Windows.UI.Xaml.Media namespace
Two sets of classes define a region of space in XAML UI: Shape classes and Geometry classes.
The main difference between these classes is that a Shape has a brush associated with it and can be rendered to the screen, and a Geometry simply defines a region of space and is not rendered unless it helps contribute information to another UI property. You can think of a Shape as a UIElement with its boundary defined by a Geometry.
This topic covers mainly the Shape classes.
The Shape classes are Line, Ellipse, Rectangle, Polygon, Polyline, and Path.
Path is interesting because it can define an arbitrary geometry, and the Geometry class манежи пренатал involved here because манежи пренатал one way to define the parts of a Path.
For a Shape to render to the app canvas, you must associate a Brush with it.
Set the Fill property of the Shape to the Brush you want. For more info about brushes, see Using brushes.
A Shape can манежи пренатал have a Stroke, which is a line that is drawn around the shape's perimeter. A Stroke also requires a манежи пренатал that defines its appearance, and should have a non-zero value for манежи пренатал.
StrokeThickness is a property that defines the perimeter's thickness around the shape edge. If you don't specify a Brush value манежи пренатал Stroke, or if you set манежи пренатал to 0, then the border around the shape is not drawn.
An Ellipse is a shape with a curved perimeter.
To create a basic Ellipse, specify a Width, Height, and a Brush for the Fill.
The next example creates an Ellipse with a Width of 200 and a Height of 200, and uses a SteelBlue colored SolidColorBrush as its Fill.
Here's the rendered Ellipse.
In this манежи пренатал the Ellipse is what most people would consider a circle, but that's how you declare a circle shape in XAML: use an Ellipse with манежи пренатал Width and Height.
When an Ellipse is positioned in a UI layout, its size is assumed to be the same as a rectangle with that Width and Height; the area outside the perimeter does not have rendering but still is part of its layout slot size.
A set of 6 Ellipse elements are part of the control template for the ProgressRing control, and 2 concentric Ellipse elements are part of a RadioButton.
A Rectangle is a four-sided shape with its opposite sides being equal.
Манежи пренатал create a basic Rectangle, specify a Width, a Height, and a Fill.
You can round the corners of a Rectangle.
To create rounded corners, specify a value for the RadiusX and RadiusY properties. These properties specify the x-axis and y-axis of an ellipse that defines манежи пренатал curve of the corners. The maximum allowed value of RadiusX is the Width divided by two and the maximum allowed value of RadiusY is the Height divided by two.
The next example creates a Rectangle with a Width of 200 and a Height of 100.
It uses a Blue value of SolidColorBrush for its Fill and a Black value of SolidColorBrush for its Stroke. We set the StrokeThickness to 3. We set the RadiusX property to 50 and the RadiusY property to 10, which gives the Rectangle rounded corners.
Here's the rendered Rectangle.
Tip There are some scenarios for UI definitions where instead манежи пренатал using a Rectangle, a Border might манежи пренатал more appropriate.
If your intention is to create a rectangle shape around other content, it might be better to use Border because it can have child content and will automatically size around that content, rather than using the fixed dimensions for height and width like Rectangle does.
A Border also has the option of having rounded corners if you set the CornerRadius property.
On манежи пренатал other hand, a Rectangle is probably a better choice for control composition. A Rectangle shape is seen in many control templates because it's used as a "FocusVisual" part манежи пренатал focusable controls.
Whenever the control is in a "Focused" visual state, this rectangle is made visible, in other states it's hidden.
A Polygon is a shape with a boundary defined by an arbitrary number of points. The boundary is created by connecting a line from one point to the next, with the last point connected to the first point. The Points property манежи пренатал the collection of points that make up the boundary.
In XAML, you define the points with a comma-separated list. In code-behind you use a PointCollection to define the points and you add each individual point as a Point value to the collection.
You don't need to explicitly declare the points such that the start point and end point are both specified as the same Point value. The rendering logic for a Polygon assumes that you are defining a closed shape and will connect the end point to the start point implicitly.
The next example creates a Polygon with 4 points set to,and.
It uses a LightBlue value of SolidColorBrush for its Fill, and has no value for Stroke so it has no perimeter outline.
Here's the rendered Polygon.
Tip A Point value is often used as a type in XAML for scenarios other than declaring the vertices of shapes.
For example, a Point is part of манежи пренатал event data for touch events, so you can know exactly where in a coordinate space the touch action occurred. For more info about Point and how to use it in XAML or code, see the API reference topic for Point.
A манежи пренатал is simply a line drawn between two points in coordinate space.
A Line ignores any value provided for Fill, because it has no interior space. For a Line, make sure to specify values for the Stroke and StrokeThickness properties, because otherwise the Line won't render.
You don't use Point values to specify a Line shape, instead you use discrete Double values for X1, Y1, X2 and Y2.
This enables minimal markup for horizontal or vertical lines. For example, defines a horizontal line that is 400 pixels long. The other X,Y properties are 0 by default, so in terms of points this XAML would draw a line from to. You could then use a TranslateTransform манежи пренатал move the entire Line, if you wanted it to start at a point other than (0,0).
A Polyline манежи пренатал similar to a Polygon in that the boundary of the shape is defined by a set of points, except the last point манежи пренатал a Polyline is not connected to the first point.
Note You could explicitly have an манежи пренатал start point and end point in the Points set for the Polyline, but in манежи пренатал case you probably could have used a Polygon instead.
If you specify a Fill of a Polyline, the Fill paints the interior space of the shape, even if the start point and end point of the Points set for the Polyline do not intersect.
If you do not specify a Fill, then the Polyline is similar to what would have rendered if you had specified several individual Line elements where the start points and end points of consecutive lines intersected.
As with манежи пренатал Polygon, the Points property defines the collection of points that make up манежи пренатал boundary.
In XAML, you define the points with a comma-separated list. In code-behind, you use a PointCollection to define the points and you add each individual point манежи пренатал a Point structure to the collection.
This example creates a Polyline with four points set to,and манежи пренатал.
A Stroke is defined but not a Fill.
Here's the rendered Polyline. Notice that the first and last points are not connected by the Stroke outline as they are in a Polygon.
A Path is манежи пренатал most versatile Shape because you can use it to define an arbitrary geometry.
But with this versatility comes complexity. Let's now look at how to create a basic Path in XAML.
You define the geometry of a path with the Data property. There are two techniques for setting Data:
In this form, the Path.Data value is consuming a serialization format манежи пренатал graphics. You typically don't text-edit this value in string form after it is first established.
Instead, you use design tools that enable you to work in a design or drawing metaphor on a surface. Then you save манежи пренатал export the output, and this gives you a XAML file or XAML манежи пренатал fragment with Path.Data information.
This can be done in code or in XAML. That single Geometry is typically a GeometryGroup, which acts as a container that can composite multiple geometry definitions into a single object for purposes of the object model.
The most common reason for doing this is because you want to use one or more of the curves and complex shapes that can be defined as Segments values for a PathFigure, for example BezierSegment.
This example shows a Path that might have resulted from using Blend for Visual Studio to produce just a few vector shapes and then saving the result as XAML.
The total Path consists of a Bezier curve segment and a line segment. The example is mainly intended to give you some examples of what elements exist in the Path.Data serialization format and what the numbers represent.
This Data begins with the move command, indicated by "M", which establishes an манежи пренатал start point for the path.
The first segment is a cubic Bezier манежи пренатал that begins at and ends at манежи пренатал, which is drawn by using the two control points and.
This segment манежи пренатал indicated by the "C" command in the Data манежи пренатал string.
The second segment begins with an absolute horizontal line command "H", which specifies a line drawn from the preceding subpath endpoint to a манежи пренатал endpoint. Because it's a horizontal line command, the value specified is an x-coordinate.
Here's the rendered Path.
The next example shows a usage of the other technique we discussed: a GeometryGroup with a PathGeometry.
This example exercises some of the contributing geometry types that can be used as part of манежи пренатал PathGeometry: PathFigure and the various elements that can be a segment in PathFigure.Segments.
Here's the rendered Path.
Using PathGeometry may be more readable than populating a Path.Data string.
On the other hand, Path.Data uses a syntax compatible with Scalable Vector Graphics (SVG) image path definitions so it may be useful for porting graphics from SVG, or as output from a tool like Манежи пренатал https://docs.microsoft.com/en-us/windows/uwp/design/controls-and-patterns/shapes