\name{layTrack-methods}
\docType{methods}
\alias{layTrack}
\alias{layTrack-methods}
\alias{layTrack,browserSession,trackSet-method}
\alias{layTrack,browserSession,trackSets-method}
\alias{layTrack,ucscSession,trackSets-method}
\alias{layTrack,argoSession,trackSet-method}
\title{ Laying tracks }
\description{
  Methods for loading \code{\linkS4class{trackSet}}s into genome browsers.
}
\usage{
layTrack(object, track, name = deparse(substitute(track)), view = FALSE, ...)
}
\arguments{
  \item{object}{A \code{\linkS4class{browserSession}} into which the
    track is loaded.}
  \item{track}{The track(s) to load.}
  \item{name}{The name(s) of the track(s) being loaded.}
  \item{view}{Whether to create a view of the track after loading it.}
  \item{\dots}{Arguments to pass on to methods.}
}
\section{Methods}{
  The following methods are defined by \pkg{rtracklayer}. A browser
  session implementation must implement a method for either
  \code{trackSet} or \code{trackSets}. The base \code{browserSession}
  class will delegate appropriately.
  
  \describe{

    \item{object = "browserSession", track = "trackSet"}{ Load this
      track into the session. }

    \item{object = "browserSession", track = "trackSets"}{ Load all tracks
      into the session. }

    \item{object = "ucscSession", track = "trackSets"}{
      \code{layTrack(object, track, name = deparse(substitute(track)),
        view = FALSE, format = "gff")}:
      Load the tracks into the session using the specified
      \code{format}.
    }
    
    \item{object = "argoSession", track = "trackSet"}{
      Load the track into the session.
    }
  }
}
\seealso{\code{\link{trackSet}} for getting \code{trackSet} instances
  from a session.}
\examples{
\dontrun{
  session <- browserSession()
  track <- import(system.file("tests", "v1.gff", package = "rtracklayer"))
  layTrack(session, track, "My Track")
}
}
\keyword{methods}