gtkWidgetSetDoubleBuffered       package:RGtk2       R Documentation

_g_t_k_W_i_d_g_e_t_S_e_t_D_o_u_b_l_e_B_u_f_f_e_r_e_d

_D_e_s_c_r_i_p_t_i_o_n:

     Widgets are double buffered by default; you can use this function
     to turn off the buffering. "Double buffered" simply means that
     'gdkWindowBeginPaintRegion' and 'gdkWindowEndPaint' are called
     automatically around expose events sent to the widget.
     'gdkWindowBeginPaint()' diverts all drawing to a widget's window
     to an offscreen buffer, and 'gdkWindowEndPaint' draws the buffer
     to the screen. The result is that users see the window update in
     one smooth step, and don't see individual graphics primitives
     being rendered.

_U_s_a_g_e:

     gtkWidgetSetDoubleBuffered(object, double.buffered)

_A_r_g_u_m_e_n_t_s:

'object': ['GtkWidget']  a 'GtkWidget'

'double.buffered': [logical] 'TRUE' to double-buffer a widget

_D_e_t_a_i_l_s:

     In very simple terms, double buffered widgets don't flicker, so
     you would only use this function to turn off double buffering if
     you had special needs and really knew what you were doing.

     Note: if you turn off double-buffering, you have to handle expose
     events, since even the clearing to the background color or  pixmap
     will not happen automatically (as it is done in 
     'gdkWindowBeginPaint()').

_A_u_t_h_o_r(_s):

     Derived by RGtkGen from GTK+ documentation

