Exposes methods for offloading certain operations to the underlying IWICBitmapSource implementation.
The IWICBitmapSourceTransform interface has these methods.
|IWICBitmapSourceTransform::CopyPixels||Copies pixel data using the supplied input parameters.|
|IWICBitmapSourceTransform::DoesSupportTransform||Determines whether a specific transform option is supported natively by the implementation of the IWICBitmapSourceTransform interface.|
|IWICBitmapSourceTransform::GetClosestPixelFormat||Retrieves the closest pixel format to which the implementation of IWICBitmapSourceTransform can natively copy pixels, given a desired format.|
|IWICBitmapSourceTransform::GetClosestSize||Returns the closest dimensions the implementation can natively scale to given the desired dimensions.|
The IWICBitmapSourceTransform interface is implemented by codecs which can natively scale, flip, rotate, or format convert pixels during decoding. As the transformation is combined with the decoding process, native transformation will generally offer performance advantages over non-native transformations. The inbox IWICBitmapScaler, IWICBitmapFlipRotator, and IWICFormatConverter implementations all make use of the IWICBitmapSourceTransform interface when they are placed immediately after a supported IWICBitmapFrameDecode, so in the typical case an application will automatically receive this performance increase and does not need to directly use this interface. However, when chaining multiple transformations, or when implementing a custom transformation, there may be a performance advantage to using the IWICBitmapSourceTransform interface directly.
|Windows version||Windows XP with SP2, Windows Vista [desktop apps | UWP apps] Windows Server 2008 [desktop apps | UWP apps]|