public static IAsyncResult BeginFillEllipse(
this IReadWriteBitmapData bitmapData,
Color32 color,
Rectangle bounds,
DrawingOptions? drawingOptions = null,
AsyncConfig? asyncConfig = null
)
<ExtensionAttribute>
Public Shared Function BeginFillEllipse (
bitmapData As IReadWriteBitmapData,
color As Color32,
bounds As Rectangle,
Optional drawingOptions As DrawingOptions = Nothing,
Optional asyncConfig As AsyncConfig = Nothing
) As IAsyncResult
public:
[ExtensionAttribute]
static IAsyncResult^ BeginFillEllipse(
IReadWriteBitmapData^ bitmapData,
Color32 color,
Rectangle bounds,
DrawingOptions^ drawingOptions = nullptr,
AsyncConfig^ asyncConfig = nullptr
)
[<ExtensionAttribute>]
static member BeginFillEllipse :
bitmapData : IReadWriteBitmapData *
color : Color32 *
bounds : Rectangle *
?drawingOptions : DrawingOptions *
?asyncConfig : AsyncConfig
(* Defaults:
let _drawingOptions = defaultArg drawingOptions null
let _asyncConfig = defaultArg asyncConfig null
*)
-> IAsyncResult
When filling an ellipse, the right/bottom values of the bounding rectangle are exclusive, so if the width or height is zero, then nothing is drawn.
This method does not use optimized shortcuts. If the same ellipse is filled repeatedly, creating a Path with PreferCaching enabled and adding the ellipse to it can provide a better performance.
In .NET Framework 4.0 and above you can use also the FillEllipseAsync methods.
To finish the operation and to get the exception that occurred during the operation you have to call the EndFillEllipse 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. |