AtkAction               package:RGtk2               R Documentation

_A_t_k_A_c_t_i_o_n

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

     The ATK interface provided by UI components which the user can
     activate/interact with,

_M_e_t_h_o_d_s _a_n_d _F_u_n_c_t_i_o_n_s:

     'atkActionDoAction(object, i)'
      'atkActionGetNActions(object)'
      'atkActionGetDescription(object, i)'
      'atkActionGetName(object, i)'
      'atkActionGetLocalizedName(object, i)'
      'atkActionGetKeybinding(object, i)'
      'atkActionSetDescription(object, i, desc)'

_H_i_e_r_a_r_c_h_y:

     GInterface
        +----AtkAction 

_I_m_p_l_e_m_e_n_t_a_t_i_o_n_s:

     AtkAction is implemented by 'AtkHyperlink' and  'AtkNoOpObject'.

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

     'AtkAction' should be implemented by instances of 'AtkObject'
     classes with which the user can interact directly, i.e. buttons,
     checkboxes, scrollbars,  e.g. components which are not "passive"
     providers of UI information.

     Exceptions: when the user interaction is already covered by
     another appropriate interface such as 'AtkEditableText'
     (insert/delete test, etc.) or 'AtkValue' (set value) then these
     actions should not be exposed by 'AtkAction' as well.  

     Also note that the 'AtkAction' API is limited in that parameters
     may not be passed to the object being activated; thus the action
     must be self-contained and specifiable via only a single "verb". 
     Concrete examples include "press", "release", "click" for buttons,
     "drag" (meaning initiate drag) and "drop" for drag sources and
     drop targets, etc.  

     Though most UI interactions on components should be invocable via
     keyboard as well as mouse, there will generally be a close mapping
     between "mouse actions" that are possible on a component and the
     AtkActions.  Where mouse and keyboard actions are redundant in
     effect, 'AtkAction' should expose only one action rather than
     exposing redundant actions if possible.  By convention we have
     been using "mouse centric" terminology for 'AtkAction' names.

_S_t_r_u_c_t_u_r_e_s:


     '_A_t_k_A_c_t_i_o_n' The AtkAction structure does not contain any fields.


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

     Derived by RGtkGen from GTK+ documentation

_R_e_f_e_r_e_n_c_e_s:

     <URL: http://developer.gnome.org/doc/API/2.0/atk/AtkAction.html>

