Lines Matching full:surface
21 * drawing, the surface will be pixels, but (for example) when drawing into
22 * a PDF or Picture canvas, the surface stores the recorded commands.
24 * To draw into a canvas, first create the appropriate type of Surface, and
25 * then request the canvas from the surface.
32 * Create a new surface, using the specified pixels/rowbytes as its
35 * If the requested surface cannot be created, or the request is not a
41 * Return a new surface, with the memory for the pixels automatically
44 * If the requested surface cannot be created, or the request is not a
50 * Return a new surface whose contents will be recorded into a picture.
51 * When this surface is drawn into another canvas, its contents will be
57 * Return a new surface using the specified render target.
62 * Return a new surface whose contents will be drawn to an offscreen
63 * render target, allocated by the surface.
72 * surface. Each time the content is changed changed, either by drawing
73 * into this surface, or explicitly calling notifyContentChanged()) this
76 * If this surface is empty (i.e. has a zero-dimention), this will return
88 * Return a canvas that will draw into this surface. This will always
89 * return the same canvas for a given surface, and is manged/owned by the
90 * surface. It should not be used when its parent surface has gone out of
96 * Return a new surface that is "compatible" with this one, in that it will
97 * efficiently be able to be drawn into this surface. Typical calling
111 * Returns an image of the current state of the surface pixels up to this
112 * point. Subsequent changes to the surface (by drawing into its canvas)
119 * it seems that directly drawing a surface into another canvas might be
