Tip
See the Examples section of the AsyncHelper
class for details about how to create a context for possibly async top level methods.
public static IReadWriteBitmapData? Clone(
this IReadableBitmapData source,
IAsyncContext? context,
Rectangle? sourceRectangle = null
)
<ExtensionAttribute>
Public Shared Function Clone (
source As IReadableBitmapData,
context As IAsyncContext,
Optional sourceRectangle As Rectangle? = Nothing
) As IReadWriteBitmapData
public:
[ExtensionAttribute]
static IReadWriteBitmapData^ Clone(
IReadableBitmapData^ source,
IAsyncContext^ context,
Nullable<Rectangle> sourceRectangle = nullptr
)
[<ExtensionAttribute>]
static member Clone :
source : IReadableBitmapData *
context : IAsyncContext *
?sourceRectangle : Nullable<Rectangle>
(* Defaults:
let _sourceRectangle = defaultArg sourceRectangle null
*)
-> IReadWriteBitmapData
This method blocks the caller thread but if context belongs to an async top level method, then the execution may already run on a pool thread. Degree of parallelism, the ability of cancellation and reporting progress depend on how these were configured at the top level method. To reconfigure the degree of parallelism of an existing context, you can use the AsyncContextWrapper class.
Alternatively, you can use this method to specify the degree of parallelism for synchronous execution. For example, by passing AsyncHelper.SingleThreadContext to the context parameter the method will be forced to use a single thread only.
When reporting progress, this library always passes a DrawingOperation instance to the generic methods of the IAsyncProgress interface.
ArgumentNullException | source is . |
ArgumentOutOfRangeException | sourceRectangle has no overlapping region with source bounds. |