gdkWindowSetDebugUpdates        package:RGtk2        R Documentation

_g_d_k_W_i_n_d_o_w_S_e_t_D_e_b_u_g_U_p_d_a_t_e_s

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

     With update debugging enabled, calls to
     'gdkWindowInvalidateRegion' clear the invalidated region of the
     screen to a noticeable color, and GDK pauses for a short time
     before sending exposes to windows during
     'gdkWindowProcessUpdates'.  The net effect is that you can see the
     invalid region for each window and watch redraws as they occur.
     This allows you to diagnose inefficiencies in your application.

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

     gdkWindowSetDebugUpdates(setting)

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

'setting': [logical] 'TRUE' to turn on update debugging

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

     In essence, because the GDK rendering model prevents all flicker,
     if you are redrawing the same region 400 times you may never
     notice, aside from noticing a speed problem. Enabling update
     debugging causes GTK to flicker slowly and noticeably, so you can
     see exactly what's being redrawn when, in what order.

     The -gtk-debug=updates command line option passed to GTK+ programs
     enables this debug option at application startup time. That's
     usually more useful than calling 'gdkWindowSetDebugUpdates'
     yourself, though you might want to use this function to enable
     updates sometime after application startup time.

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

     Derived by RGtkGen from GTK+ documentation

