cairo-Error-Handling          package:RGtk2          R Documentation

_E_r_r_o_r _h_a_n_d_l_i_n_g

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

     Decoding cairo's status

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

     'cairoStatusToString(status)'

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

     Cairo uses a single status type to represent all kinds of errors. 
     A status value of 'CAIRO_STATUS_SUCCESS' represents no error and
     has an integer value of zero.  All other status values represent
     an error.

     Cairo's error handling is designed to be easy to use and safe. 
     All major cairo objects retain an error status internally which
     can be queried anytime by the users using cairo*'status()' calls. 
     In the mean time, it is safe to call all cairo functions normally
     even if the underlying object is in an error status.  This means
     that no error handling code is required before or after each
     individual cairo function call.

_E_n_u_m_s _a_n_d _F_l_a_g_s:


     '_C_a_i_r_o_S_t_a_t_u_s' 'CairoStatus' is used to indicate errors that can
          occur when using Cairo. In some cases it is returned directly
          by functions. but when using 'Cairo', the last error, if any,
          is stored in the context and can be retrieved with
          'cairoStatus'.

          New entries may be added in future versions.  Use
          'cairoStatusToString' to get a human-readable representation
          of an error message.  

          '_s_u_c_c_e_s_s' no error has occurred

          '_n_o-_m_e_m_o_r_y' out of memory

          '_i_n_v_a_l_i_d-_r_e_s_t_o_r_e' 'cairoRestore' called without matching
               'cairoSave'

          '_i_n_v_a_l_i_d-_p_o_p-_g_r_o_u_p' no saved group to pop

          '_n_o-_c_u_r_r_e_n_t-_p_o_i_n_t' no current point defined

          '_i_n_v_a_l_i_d-_m_a_t_r_i_x' invalid matrix (not invertible)

          '_i_n_v_a_l_i_d-_s_t_a_t_u_s' invalid value for an input 'CairoStatus'

          '_n_u_l_l-_p_o_i_n_t_e_r' 'NULL' pointer

          '_i_n_v_a_l_i_d-_s_t_r_i_n_g' input string not valid UTF-8

          '_i_n_v_a_l_i_d-_p_a_t_h-_d_a_t_a' input path data not valid

          '_r_e_a_d-_e_r_r_o_r' error while reading from input stream

          '_w_r_i_t_e-_e_r_r_o_r' error while writing to output stream

          '_s_u_r_f_a_c_e-_f_i_n_i_s_h_e_d' target surface has been finished

          '_s_u_r_f_a_c_e-_t_y_p_e-_m_i_s_m_a_t_c_h' the surface type is not appropriate
               for the operation

          '_p_a_t_t_e_r_n-_t_y_p_e-_m_i_s_m_a_t_c_h' the pattern type is not appropriate
               for the operation

          '_i_n_v_a_l_i_d-_c_o_n_t_e_n_t' invalid value for an input 'CairoContent'

          '_i_n_v_a_l_i_d-_f_o_r_m_a_t' invalid value for an input 'CairoFormat'

          '_i_n_v_a_l_i_d-_v_i_s_u_a_l' invalid value for an input Visual*

          '_f_i_l_e-_n_o_t-_f_o_u_n_d' file not found

          '_i_n_v_a_l_i_d-_d_a_s_h' invalid value for a dash setting

          '_i_n_v_a_l_i_d-_d_s_c-_c_o_m_m_e_n_t' invalid value for a DSC comment (Since
               1.2)

          '_i_n_v_a_l_i_d-_i_n_d_e_x' invalid index passed to getter (Since 1.4)

          '_c_l_i_p-_n_o_t-_r_e_p_r_e_s_e_n_t_a_b_l_e' clip region not representable in
               desired format (Since 1.4)


_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://www.cairographics.org/manual/cairo-Error-Handling.html>

