\HeaderA{glines-methods}{Drawing filter boundaries}{glines.Rdash.methods}
\aliasA{glines}{glines-methods}{glines}
\aliasA{glines,curv1Filter,ANY-method}{glines-methods}{glines,curv1Filter,ANY.Rdash.method}
\aliasA{glines,curv1Filter,flowFrame-method}{glines-methods}{glines,curv1Filter,flowFrame.Rdash.method}
\aliasA{glines,curv1Filter,missing-method}{glines-methods}{glines,curv1Filter,missing.Rdash.method}
\aliasA{glines,curv1Filter,multipleFilterResult-method}{glines-methods}{glines,curv1Filter,multipleFilterResult.Rdash.method}
\aliasA{glines,curv2Filter,ANY-method}{glines-methods}{glines,curv2Filter,ANY.Rdash.method}
\aliasA{glines,curv2Filter,flowFrame-method}{glines-methods}{glines,curv2Filter,flowFrame.Rdash.method}
\aliasA{glines,curv2Filter,multipleFilterResult-method}{glines-methods}{glines,curv2Filter,multipleFilterResult.Rdash.method}
\aliasA{glines,ellipsoidGate,character-method}{glines-methods}{glines,ellipsoidGate,character.Rdash.method}
\aliasA{glines,ellipsoidGate,filterResult-method}{glines-methods}{glines,ellipsoidGate,filterResult.Rdash.method}
\aliasA{glines,ellipsoidGate,flowFrame-method}{glines-methods}{glines,ellipsoidGate,flowFrame.Rdash.method}
\aliasA{glines,filter,missing-method}{glines-methods}{glines,filter,missing.Rdash.method}
\aliasA{glines,filterResult,ANY-method}{glines-methods}{glines,filterResult,ANY.Rdash.method}
\aliasA{glines,filterResult,flowFrame-method}{glines-methods}{glines,filterResult,flowFrame.Rdash.method}
\aliasA{glines,kmeansFilter,ANY-method}{glines-methods}{glines,kmeansFilter,ANY.Rdash.method}
\aliasA{glines,norm2Filter,ANY-method}{glines-methods}{glines,norm2Filter,ANY.Rdash.method}
\aliasA{glines,norm2Filter,flowFrame-method}{glines-methods}{glines,norm2Filter,flowFrame.Rdash.method}
\aliasA{glines,norm2Filter,logicalFilterResult-method}{glines-methods}{glines,norm2Filter,logicalFilterResult.Rdash.method}
\aliasA{glines,polygonGate,character-method}{glines-methods}{glines,polygonGate,character.Rdash.method}
\aliasA{glines,polygonGate,filterResult-method}{glines-methods}{glines,polygonGate,filterResult.Rdash.method}
\aliasA{glines,polygonGate,flowFrame-method}{glines-methods}{glines,polygonGate,flowFrame.Rdash.method}
\aliasA{glines,quadGate,character-method}{glines-methods}{glines,quadGate,character.Rdash.method}
\aliasA{glines,quadGate,filterResult-method}{glines-methods}{glines,quadGate,filterResult.Rdash.method}
\aliasA{glines,quadGate,flowFrame-method}{glines-methods}{glines,quadGate,flowFrame.Rdash.method}
\aliasA{glines,rectangleGate,character-method}{glines-methods}{glines,rectangleGate,character.Rdash.method}
\aliasA{glines,rectangleGate,filterResult-method}{glines-methods}{glines,rectangleGate,filterResult.Rdash.method}
\aliasA{glines,rectangleGate,flowFrame-method}{glines-methods}{glines,rectangleGate,flowFrame.Rdash.method}
\keyword{methods}{glines-methods}
\begin{Description}\relax
These methods extend the basic graphics
\code{\LinkA{lines}{lines}} methods for drawing of
\code{\LinkA{filter}{filter}} boundaries. They allow for
multiple dispatch, since not all \code{\LinkA{filter}{filter}}
types need to be evaluated for plotting, but this decision should be
made internally.
\end{Description}
\begin{Details}\relax
When plotting
code{\LinkA{flowFrame}{flowFrame}}s using the
\code{plot} or \code{xyplot }methods provided by \code{flowViz}, the
plotted parameters are recorded, which makes it possible to correctly
overlay the outlines of \code{\LinkA{filter}{filter}}s
assuming that they are defined for the repective parameters. Warnings
and error will be cast for the cases where the parameters are
non-distinct or ambigious.

The flow parameters plotted can be passed on to any of the methods
through the optional \code{channels} argument, which always gets
precedence over automatically detected parameters.

The methods support all plotting parameters that are available for the
code{base} \code{lines} functions.
\end{Details}
\begin{Section}{Methods}
\describe{

\item[x = "filter", data = "missing"] General method for all
objects inheriting from
\code{\LinkA{filter}{filter}}. This is used as the
default when no more explicit method is found. It tries to find
the plotted parameters from the internal \code{flowViz.state}
environment. This only works if the flow data has been plotted
using the \code{plot} or \code{xyplot} methods provided by this
\code{flowViz} package. 

\item[x = "filterResult", data = "ANY"] General method for all
\code{\LinkA{filterResult}{filterResult}}
object. This basically extracts the
\code{\LinkA{filter}{filter}} from the
\code{\LinkA{filterResult}{filterResult}} and
dispatches on that. 

\item[x = "filterResult", data = "flowFrame"] For some
\code{\LinkA{filter}{filter}} types we need the raw
data to re-evaluate the filter. 

\item[x = "curv1Filter", data = "ANY"] We either need a
\code{\LinkA{filterResult}{filterResult}} or the raw
data as a \code{\LinkA{flowFrame}{flowFrame}} for
\code{\LinkA{curv1Filter}{curv1Filter}}s. 

\item[x = "curv1Filter", data = "flowFrame"] see above 

\item[x = "curv1Filter", data = "missing"] see above 

\item[x = "curv1Filter", data = "multipleFilterResult"] see above 

\item[x = "curv2Filter", data = "ANY"] We either need a
\code{\LinkA{filterResult}{filterResult}} or the raw
data as a \code{\LinkA{flowFrame}{flowFrame}} for
\code{\LinkA{curv2Filter}{curv2Filter}}s.

\item[x = "curv2Filter", data = "flowFrame"] see above 

\item[x = "curv2Filter", data = "multipleFilterResult"] see above 

\item[x = "kmeansFilter", data = "ANY"] We don't know how to plot
outlines of a
\code{\LinkA{kmeansFilter}{kmeansFilter}}, hence we
warn. 

\item[x = "norm2Filter", data = "ANY"] We either need a
\code{\LinkA{filterResult}{filterResult}} or the raw
data as a \code{\LinkA{flowFrame}{flowFrame}} for
\code{\LinkA{norm2Filter}{norm2Filter}}s.

\item[x = "norm2Filter", data = "flowFrame"] see above 

\item[x = "norm2Filter", data = "logicalFilterResult"] see above 

\item[x = "polygonGate", data = "character"] We can plot a
\code{\LinkA{polygonGate}{polygonGate}} directly from the gate
definition. 

\item[x = "polygonGate", data = "filterResult"] see above 

\item[x = "polygonGate", data = "flowFrame"] see above 

\item[x = "quadGate", data = "character"] We can plot a
\code{\LinkA{quadGate}{quadGate}} directly from the gate
definition. 

\item[x = "quadGate", data = "filterResult"] see above 

\item[x = "quadGate", data = "flowFrame"] see above 

\item[x = "rectangleGate", data = "character"] We can plot a
\code{\LinkA{rectangleGate}{rectangleGate}} directly from the gate
definition. 

\item[x = "rectangleGate", data = "filterResult"] see above 

\item[x = "rectangleGate", data = "flowFrame"] see above 

\item[x = "ellipsoidGate", data = "character"] We can plot a
\code{\LinkA{rectangleGate}{rectangleGate}} directly from the gate
definition. 

\item[x = "ellipsoidGate", data = "filterResult"] see above 

\item[x = "ellipsoidGate", data = "flowFrame"] see above 


}
\end{Section}
\begin{Author}\relax
F. Hahne
\end{Author}
\begin{SeeAlso}\relax
\code{\LinkA{filter}{filter}},
\code{\LinkA{flowFrame}{flowFrame}},
\code{\LinkA{glines}{glines}}, \code{\LinkA{gpoints}{gpoints}}
\end{SeeAlso}

