/
updateDragulaInput.Rd
104 lines (87 loc) · 2.97 KB
/
updateDragulaInput.Rd
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
% Generated by roxygen2: do not edit by hand
% Please edit documentation in R/input-dragula.R
\name{updateDragulaInput}
\alias{updateDragulaInput}
\title{Update Dragula Input}
\usage{
updateDragulaInput(
session,
inputId,
choices = NULL,
choiceNames = NULL,
choiceValues = NULL,
selected = NULL,
selectedNames = NULL,
selectedValues = NULL,
badge = TRUE,
status = "primary"
)
}
\arguments{
\item{session}{The \code{session} object passed to function given to \code{shinyServer}.}
\item{inputId}{The \code{input} slot that will be used to access the value.}
\item{choices}{List of values to select from (if elements of the list are
named then that name rather than the value is displayed to the user).
If this argument is provided, then \code{choiceNames} and \code{choiceValues} must
not be provided, and vice-versa. The values should be strings; other
types (such as logicals and numbers) will be coerced to strings.}
\item{choiceNames, choiceValues}{List of names and values, respectively,
that are displayed to the user in the app and correspond to the each
choice (for this reason, \code{choiceNames} and \code{choiceValues} must have the same length).
If either of these arguments is provided, then the other must be provided and
choices must not be provided. The advantage of using both of these over a named
list for choices is that \code{choiceNames} allows any type of UI object to be passed
through (tag objects, icons, HTML code, ...), instead of just simple text.}
\item{selected}{Default selected values. Must be a \code{list} with \code{targetsIds} as names.}
\item{selectedNames, selectedValues}{Update selected items with custom names and values.}
\item{badge}{Displays choices inside a Bootstrap badge. Use \code{FALSE}
if you want to pass custom appearance with \code{choiceNames}.}
\item{status}{If choices are displayed into a Bootstrap label, you can use Bootstrap
status to color them, or \code{NULL}.}
}
\description{
Update \code{\link[=dragulaInput]{dragulaInput()}} widget server-side.
}
\examples{
if (interactive()) {
library("shiny")
library("esquisse")
ui <- fluidPage(
tags$h2("Update dragulaInput"),
radioButtons(
inputId = "update",
label = "Dataset",
choices = c("iris", "mtcars")
),
tags$br(),
dragulaInput(
inputId = "myDad",
sourceLabel = "Variables",
targetsLabels = c("X", "Y", "fill", "color", "size"),
choices = names(iris),
replace = TRUE, width = "400px", status = "success"
),
verbatimTextOutput(outputId = "result")
)
server <- function(input, output, session) {
output$result <- renderPrint(str(input$myDad))
observeEvent(input$update, {
if (input$update == "iris") {
updateDragulaInput(
session = session,
inputId = "myDad",
choices = names(iris),
status = "success"
)
} else {
updateDragulaInput(
session = session,
inputId = "myDad",
choices = names(mtcars)
)
}
}, ignoreInit = TRUE)
}
shinyApp(ui, server)
}
}