Lines Matching refs:is
15 everything is in fact first drawn on an in-memory buffer (a
17 associated wxDC, only once, when this object is destroyed. wxBufferedDC itself
18 is typically associated with \helpref{wxClientDC}{wxclientdc}, if you want to
29 There is another possible use for wxBufferedDC is to use it to maintain a
76 flushed to this DC when this object is destroyed. You may pass NULL
79 \docparam{area}{The size of the bitmap to be used for buffering (this bitmap is
80 created internally when it is not given explicitly).}
82 \docparam{buffer}{Explicitly provided bitmap to be used for buffering: this is
84 time but it also requires more memory as the bitmap is never freed. The bitmap
85 should have appropriate size, anything drawn outside of its bounds is clipped.}
88 the window is buffered, or wxBUFFER\_VIRTUAL\_AREA to indicate that the buffer bitmap
89 covers the virtual area (in which case PrepareDC is automatically called for the actual window
115 This is a subclass of \helpref{wxBufferedDC}{wxbuffereddc} which can be used
118 is called with wxBG\_STYLE\_CUSTOM somewhere in the class initialization code, and that's all
119 you have to do to (mostly) avoid flicker. The only thing to watch out for is that if you are
152 the latter case, the size of the client part of the window is used).
155 the window is buffered, or wxBUFFER\_VIRTUAL\_AREA to indicate that the buffer bitmap
156 covers the virtual area (in which case PrepareDC is automatically called for the actual window
171 and make sure \helpref{wxWindow::SetBackgroundStyle}{wxwindowgetbackgroundstyle} is called
176 is the lightweigthness - on platforms which have native double-buffering, wxAutoBufferedPaintDC is simply
177 a typedef of wxPaintDC. Otherwise, it is a typedef of wxBufferedPaintDC.