public static IAsyncResult BeginFillPie(
this IReadWriteBitmapData bitmapData,
Color32 color,
Rectangle bounds,
float startAngle,
float sweepAngle,
DrawingOptions? drawingOptions = null,
AsyncConfig? asyncConfig = null
)
<ExtensionAttribute>
Public Shared Function BeginFillPie (
bitmapData As IReadWriteBitmapData,
color As Color32,
bounds As Rectangle,
startAngle As Single,
sweepAngle As Single,
Optional drawingOptions As DrawingOptions = Nothing,
Optional asyncConfig As AsyncConfig = Nothing
) As IAsyncResult
public:
[ExtensionAttribute]
static IAsyncResult^ BeginFillPie(
IReadWriteBitmapData^ bitmapData,
Color32 color,
Rectangle bounds,
float startAngle,
float sweepAngle,
DrawingOptions^ drawingOptions = nullptr,
AsyncConfig^ asyncConfig = nullptr
)
[<ExtensionAttribute>]
static member BeginFillPie :
bitmapData : IReadWriteBitmapData *
color : Color32 *
bounds : Rectangle *
startAngle : float32 *
sweepAngle : float32 *
?drawingOptions : DrawingOptions *
?asyncConfig : AsyncConfig
(* Defaults:
let _drawingOptions = defaultArg drawingOptions null
let _asyncConfig = defaultArg asyncConfig null
*)
-> IAsyncResult
The pie shape is defined by an arc of an ellipse and the two radial lines that intersect with the endpoints of the arc.
This method does not use optimized shortcuts. If the same pie shape is filled repeatedly, creating a Path with PreferCaching enabled and adding the pie to it can provide a better performance.
In .NET Framework 4.0 and above you can use also the FillPieAsync methods.
To finish the operation and to get the exception that occurred during the operation you have to call the EndFillPie method.
This method is not a blocking call even if the MaxDegreeOfParallelism property of the asyncConfig parameter is 1.
ArgumentNullException | bitmapData is . |
OverflowException | The coordinates (after a possible transformation specified in drawingOptions) are outside the bounds of an int value. |