|
|
Line 183: |
Line 183: |
|
| |
|
| Causes the context specified to be destroyed. The memory pointed to by context may be freed and accesses are undefined. | | Causes the context specified to be destroyed. The memory pointed to by context may be freed and accesses are undefined. |
|
| |
| === Notification a Context was Displayed ===
| |
|
| |
| Video players, video games, and other timing sensitive plugins typically adjust their simulation to adapt to the speed at which frames are placed on the screen. A call from the renderer indicating when the bits from a context have reached the screen is needed.
| |
|
| |
| <pre>
| |
| void NPP_DeviceContextDisplayed(NPP instance)
| |
| </pre>
| |
|
| |
| * The renderer informs the plugin that the last published device context was displayed on the screen.
| |
| * For performance we will most likely want to be able to call NPN_GetDeviceContext before the NPP_DeviceContextDisplayed call from the previous NPN_PublishDeviceContext has arrived.
| |
| * This API could also perhaps be done through an NPEvent of the appropriate type.
| |
|
| |
|
| === Optimizations and Legacy APIs === | | === Optimizations and Legacy APIs === |