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. |
All Microsoft® Direct3D® Mobile applications are written Windows applications. This means that their entry point is WinMainand they can use all of the standard Windows Embedded CE APIs to access storage, network connections, and other services. The thing that makes Direct3 Mobile application stand apart is that instead of using windows, USER, and graphics device interface (GDI) calls to display images on the screen, they make Direct3D Mobile calls.
To start Direct3D Mobile for you application call Direct3DMobileCreate. This function will verify that the correct Direct3D Mobile runtime libraries are present in the OS, that the calling application is the only Direct3D Mobile application running on the Windows Embedded CE-based device, create a Direct3D Mobile object for the application, and return a pointer to the IDirect3DMobileinterface for the object. Your application will use this interface pointer for all global settings and capabilities relating to Direct3D Mobile overall.
Individual drawing commands are handled through calls to an IDirect3DMobileDeviceinterface representing a display driver. This is really the central interface for Direct3D Mobile and it is the one that your application will interact with the most. For more information, see Direct3D Mobile Devices.