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? Resize(
this IReadableBitmapData source,
IAsyncContext? context,
Size newSize,
ScalingMode scalingMode = ScalingMode.Auto,
bool keepAspectRatio = false
)<ExtensionAttribute>
Public Shared Function Resize (
source As IReadableBitmapData,
context As IAsyncContext,
newSize As Size,
Optional scalingMode As ScalingMode = ScalingMode.Auto,
Optional keepAspectRatio As Boolean = false
) As IReadWriteBitmapDatapublic:
[ExtensionAttribute]
static IReadWriteBitmapData^ Resize(
IReadableBitmapData^ source,
IAsyncContext^ context,
Size newSize,
ScalingMode scalingMode = ScalingMode::Auto,
bool keepAspectRatio = false
)[<ExtensionAttribute>]
static member Resize :
source : IReadableBitmapData *
context : IAsyncContext *
newSize : Size *
?scalingMode : ScalingMode *
?keepAspectRatio : bool
(* Defaults:
let _scalingMode = defaultArg scalingMode ScalingMode.Auto
let _keepAspectRatio = defaultArg keepAspectRatio false
*)
-> 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 | newSize is invalid
-or- scalingMode has an unsupported value. |