See Also
 Important: |
|---|
| This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
A surface represents a linear area of display memory. A surface usually resides in the display memory of the display card, although surfaces can exist in system memory. Surface objects are contained within the IDirect3DMobileSurfaceinterface.
An IDirect3DMobileSurfaceinterface is obtained by calling one of the following methods:
-
IDirect3DMobileDevice::CreateDepthStencilSurface
-
IDirect3DMobileDevice::CreateImageSurface
-
IDirect3DMobileDevice::CreateRenderTarget
-
IDirect3DMobileDevice::GetBackBuffer
-
IDirect3DMobileDevice::GetDepthStencilSurface
-
IDirect3DMobileDevice::GetFrontBuffer
-
IDirect3DMobileDevice::GetRenderTarget
-
IDirect3DMobileSwapChain::GetBackBuffer
-
IDirect3DMobileTexture::GetSurfaceLevel
The IDirect3DMobileSurfaceinterface enables you to indirectly access memory through the IDirect3DMobileDevice::CopyRectsmethod. This method allows you to copy a rectangular region of pixels from one IDirect3DMobileSurfaceinterface to another IDirect3DMobileSurfaceinterface. The surface interface also has methods to directly access display memory. For example, you can use the IDirect3DMobileSurface::LockRectmethod to lock a rectangular region of display memory. It is important to call IDirect3DMobileSurface::UnlockRectafter you are done working with the locked rectangular region on the surface.
See Also
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.