1,295
edits
NPAPI:AsyncDrawing: Difference between revisions
Jump to navigation
Jump to search
→General Async Drawing Mechanics
No edit summary |
|||
| Line 90: | Line 90: | ||
Surfaces cannot be modified while they are current. A modified rectangle may be provided in the <code>changed</code> argument to give the host a hint on which part of the surface was modified with respect to the previous current surface so that the browser can choose to optimize the composition process. There is no guarantee only this rectangle will be recomposed though and the entire surface needs to be valid. | Surfaces cannot be modified while they are current. A modified rectangle may be provided in the <code>changed</code> argument to give the host a hint on which part of the surface was modified with respect to the previous current surface so that the browser can choose to optimize the composition process. There is no guarantee only this rectangle will be recomposed though and the entire surface needs to be valid. | ||
The Init and Finalize functions must be called from the main plugin thread. The SetCurrent function may be called | The Init and Finalize functions must be called from the main plugin thread. The SetCurrent function may be called from any thread. Reentrant calls into the plugin do not occur during a SetCurrent invocation. Therefore the browser is expected to implement SetCurrent using a locking protocol that cannot block for long. For example, SetCurrent might block only while the previous surface is being read by browser compositing. | ||
= NPDrawingModelAsyncBitmapSurface = | = NPDrawingModelAsyncBitmapSurface = | ||