C# Class System.Windows.Interop.D3DImage

Shadows inherited Clone() with a strongly typed version for convenience.

Shadows inherited CloneCurrentValue() with a strongly typed version for convenience.

Locks the D3DImage While locked you can call AddDirtyRect, SetBackBuffer, and Unlock. You can also write to your back buffer. You should not write to the back buffer without being locked.

Sets a back buffer source for this D3DImage. See the 2nd overload for details.

Trys to lock the D3DImage but gives up once duration expires. Returns true if the lock was obtained. See Lock for more details.

Unlocks the D3DImage Can only be called while locked. If you have dirtied the image with AddDirtyRect, Unlocking will trigger us to copy the dirty regions from the back buffer to the front buffer. While this is taking place, Lock will block. To avoid locking indefinitely, use TryLock.

Clone overrides Not sealed to allow subclasses to clone their private data

Implementation of Freezable.CreateInstanceCore.

Freezing is not allowed because the user will always have to make changes to the object based upon IsFrontBufferAvailable. We could consider SetBackBuffer to not count as a "change" but any thread could call it and that would violate our synchronization assumptions. Sealed to prevent subclasses from modifying the correct behavior.

*** WARNING ***: This runs on the composition thread! What the composition thread calls when it wants to update D3DImage about front buffer state. It may be called multiple times with the same value. Since we're on a different thread we can't touch this, so queue a dispatcher operation.

Lock implementation shared by Lock and TryLock

The DispatcherOperation corresponding to the composition thread callback. If the back buffer version matches the current version, update the front buffer status.