gtkWidgetChildFocus          package:RGtk2          R Documentation

_g_t_k_W_i_d_g_e_t_C_h_i_l_d_F_o_c_u_s

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

     This function is used by custom widget implementations; if you're
     writing an app, you'd use 'gtkWidgetGrabFocus' to move the focus
     to a particular widget, and 'gtkContainerSetFocusChain' to change
     the focus tab order. So you may want to investigate those
     functions instead.

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

     gtkWidgetChildFocus(object, direction)

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

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

'direction': ['GtkDirectionType']  direction of focus movement

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

     'gtkWidgetChildFocus' is called by containers as the user moves
     around the window using keyboard shortcuts. 'direction' indicates
     what kind of motion is taking place (up, down, left, right, tab
     forward, tab backward). 'gtkWidgetChildFocus' emits the '"focus"'"
     signal; widgets override the default handler for this signal in
     order to implement appropriate focus behavior.

     The default ::focus handler for a widget should return 'TRUE' if
     moving in 'direction' left the focus on a focusable location
     inside that widget, and 'FALSE' if moving in 'direction' moved the
     focus outside the widget. If returning 'TRUE', widgets normally
     call 'gtkWidgetGrabFocus' to place the focus accordingly; if
     returning 'FALSE', they don't modify the current focus location.

     This function replaces 'gtkContainerFocus()' from GTK+ 1.2.   It
     was necessary to check that the child was visible, sensitive,  and
     focusable before calling 'gtkContainerFocus()'. 
     'gtkWidgetChildFocus' returns 'FALSE' if the widget is not 
     currently in a focusable state, so there's no need for those
     checks.

_V_a_l_u_e:

     [logical] 'TRUE' if focus ended up inside 'widget'

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

     Derived by RGtkGen from GTK+ documentation

