mirror of
https://github.com/rstudio/shiny.git
synced 2026-01-30 17:28:32 -05:00
54 lines
1.4 KiB
R
54 lines
1.4 KiB
R
\name{updateCheckboxInput}
|
|
\alias{updateCheckboxInput}
|
|
\title{Change the value of a checkbox input on the client}
|
|
\usage{
|
|
updateCheckboxInput(session, inputId, label = NULL,
|
|
value = NULL)
|
|
}
|
|
\arguments{
|
|
\item{session}{The \code{session} object passed to
|
|
function given to \code{shinyServer}.}
|
|
|
|
\item{inputId}{The id of the input object.}
|
|
|
|
\item{label}{The label to set for the input object.}
|
|
|
|
\item{value}{The value to set for the input object.}
|
|
}
|
|
\description{
|
|
Change the value of a checkbox input on the client
|
|
}
|
|
\details{
|
|
The input updater functions send a message to the client,
|
|
telling it to change the settings of an input object. The
|
|
messages are collected and sent after all the observers
|
|
(including outputs) have finished running.
|
|
|
|
The syntax of these functions is similar to the functions
|
|
that created the inputs in the first place. For example,
|
|
\code{\link{numericInput}()} and
|
|
\code{updateNumericInput()} take a similar set of
|
|
arguments.
|
|
|
|
Any arguments with NULL values will be ignored; they will
|
|
not result in any changes to the input object on the
|
|
client.
|
|
}
|
|
\examples{
|
|
\dontrun{
|
|
shinyServer(function(input, output, session) {
|
|
|
|
observe({
|
|
# TRUE if input$controller is even, FALSE otherwise.
|
|
x_even <- input$controller \%\% 2 == 0
|
|
|
|
updateCheckboxInput(session, "inCheckbox", value = x_even)
|
|
})
|
|
})
|
|
}
|
|
}
|
|
\seealso{
|
|
\code{\link{checkboxInput}}
|
|
}
|
|
|