\HeaderA{lattice.options}{Low-level Options Controlling Behaviour of Lattice}{lattice.options}
\aliasA{lattice.getOption}{lattice.options}{lattice.getOption}
\keyword{dplot}{lattice.options}
\begin{Description}\relax
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.
\end{Description}
\begin{Usage}
\begin{verbatim}
lattice.options(...)
lattice.getOption(name)
\end{verbatim}
\end{Usage}
\begin{Arguments}
\begin{ldescription}
\item[\code{name}] character giving the name of a setting 
\item[\code{...}] new options can be defined, or existing ones modified, using one or
more arguments of the form \code{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.

\end{ldescription}
\end{Arguments}
\begin{Details}\relax
These functions are modeled on \code{options} and \code{getOption},
and behave similarly for the most part.  The components currently used
are not documented here, but are fairly self-explanatory.
\end{Details}
\begin{Value}
\code{lattice.getOption} returns the value of a single component,
whereas \code{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
\code{lattice.options}.  If called without any arguments, the full
list is returned.
\end{Value}
\begin{Author}\relax
Deepayan Sarkar \email{Deepayan.Sarkar@R-project.org}
\end{Author}
\begin{SeeAlso}\relax
\code{\LinkA{options}{options}}, \code{\LinkA{trellis.device}{trellis.device}},
\code{\LinkA{trellis.par.get}{trellis.par.get}}, \code{\LinkA{Lattice}{Lattice}}
\end{SeeAlso}
\begin{Examples}
\begin{ExampleCode}
str(lattice.options())
lattice.getOption("save.object")
\end{ExampleCode}
\end{Examples}

