Creates a new flipping buffer strategy for this component. The component must be a Canvas or Window.

numBuffers	the number of buffers
caps	the capabilities of the buffers
Throws	AWTException: if the capabilities supplied could not be supported or met
Throws	ClassCastException: if the component is not a canvas or window.
See also	java.awt.Canvas, java.awt.Window

return

whether the drawing buffer was lost since the last call to getDrawGraphics

return

whether the drawing buffer was recently restored from a lost state and reinitialized to the default background color (white)

Creates one or more complex, flipping buffers with the given capabilities.

numBuffers	number of buffers to create; must be greater than one
caps	the capabilities of the buffers. BufferCapabilities.isPageFlipping must be true.
Throws	AWTException: if the capabilities supplied could not be supported or met
Throws	IllegalStateException: if the component has no peer
Throws	IllegalArgumentException: if numBuffers is less than two, or if BufferCapabilities.isPageFlipping is not true.
See also	isPageFlipping()

Releases system resources currently consumed by this BufferStrategy and removes it from the associated Component. After invoking this method, getBufferStrategy will return null. Trying to use a BufferStrategy after it has been disposed will result in undefined behavior.

since

1.6

Flipping moves the contents of the back buffer to the front buffer, either by copying or by moving the video pointer.

flipAction	an integer value describing the flipping action for the contents of the back buffer. This should be one of the values of the BufferCapabilities.FlipContents property.
Throws	IllegalStateException: if the buffers have not yet been created
See also	getFlipContents()

return	direct access to the back buffer, as an image.
Throws	IllegalStateException: if the buffers have not yet been created

return

the buffering capabilities of this strategy

return

the graphics on the drawing buffer. This method may not be synchronized for performance reasons; use of this method by multiple threads should be handled at the application level. Disposal of the graphics object must be handled by the application.