lattice.options           package:lattice           R Documentation

_L_o_w-_l_e_v_e_l _O_p_t_i_o_n_s _C_o_n_t_r_o_l_l_i_n_g _B_e_h_a_v_i_o_u_r _o_f _L_a_t_t_i_c_e

_D_e_s_c_r_i_p_t_i_o_n:

     Functions to handle settings used by lattice.  Their main purpose
     is to make code maintainance easier, and users normally should not
     need to use these functions.  However, fine control at this level
     maybe useful in certain cases.

_U_s_a_g_e:

     lattice.options(...)
     lattice.getOption(name)

_A_r_g_u_m_e_n_t_s:

    name: character giving the name of a setting 

     ...: new options can be defined, or existing ones modified, using
          one or more arguments of the form 'name = value' or by
          passing a list of such tagged values.  Existing values can be
          retrieved by supplying the names (as character strings) of
          the components as unnamed arguments. 

_D_e_t_a_i_l_s:

     These functions are modeled on 'options' and 'getOption', and
     behave similarly for the most part.  The components currently used
     are not documented here, but are fairly self-explanatory.

_V_a_l_u_e:

     'lattice.getOption' returns the value of a single component,
     whereas 'lattice.options' always returns a list with one or more
     named components.  When changing the values of components, the old
     values of the modified components are returned by
     'lattice.options'.  If called without any arguments, the full list
     is returned.

_A_u_t_h_o_r(_s):

     Deepayan Sarkar deepayan@stat.wisc.edu

_S_e_e _A_l_s_o:

     'options', 'trellis.device', 'trellis.par.get', 'Lattice'

_E_x_a_m_p_l_e_s:

     str(lattice.options())
     lattice.getOption("save.object")

