-
-
Notifications
You must be signed in to change notification settings - Fork 31
/
Copy pathdccRangeSlider.Rd
137 lines (106 loc) · 5.31 KB
/
dccRangeSlider.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
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
% Auto-generated: do not edit by hand
\name{dccRangeSlider}
\alias{dccRangeSlider}
\title{RangeSlider component}
\description{
A double slider with two handles. Used for specifying a range of numerical values.
}
\usage{
dccRangeSlider(id=NULL, min=NULL, max=NULL, step=NULL, marks=NULL,
value=NULL, drag_value=NULL, allowCross=NULL,
className=NULL, count=NULL, disabled=NULL, dots=NULL,
included=NULL, pushable=NULL, tooltip=NULL, vertical=NULL,
verticalHeight=NULL, updatemode=NULL, loading_state=NULL,
persistence=NULL, persisted_props=NULL,
persistence_type=NULL)
}
\arguments{
\item{id}{Character. The ID of this component, used to identify dash components
in callbacks. The ID needs to be unique across all of the
components in an app.}
\item{min}{Numeric. Minimum allowed value of the slider}
\item{max}{Numeric. Maximum allowed value of the slider}
\item{step}{Numeric. Value by which increments or decrements are made}
\item{marks}{List with named elements and values of type character | lists containing elements 'label', 'style'.
those elements have the following types:
- label (character; optional)
- style (named list; optional). Marks on the slider.
The key determines the position (a number),
and the value determines what will show.
If you want to set the style of a specific mark point,
the value should be an object which
contains style and label properties.}
\item{value}{List of numerics. The value of the input}
\item{drag_value}{List of numerics. The value of the input during a drag}
\item{allowCross}{Logical. allowCross could be set as true to allow those handles to cross.}
\item{className}{Character. Additional CSS class for the root DOM node}
\item{count}{Numeric. Determine how many ranges to render, and multiple handles
will be rendered (number + 1).}
\item{disabled}{Logical. If true, the handles can't be moved.}
\item{dots}{Logical. When the step value is greater than 1,
you can set the dots to true if you want to
render the slider with dots.}
\item{included}{Logical. If the value is true, it means a continuous
value is included. Otherwise, it is an independent value.}
\item{pushable}{Logical | numeric. pushable could be set as true to allow pushing of
surrounding handles when moving an handle.
When set to a number, the number will be the
minimum ensured distance between handles.}
\item{tooltip}{Lists containing elements 'always_visible', 'placement'.
those elements have the following types:
- always_visible (logical; optional): determines whether tooltips should always be visible
(as opposed to the default, visible on hover)
- placement (a value equal to: 'left', 'right', 'top', 'bottom', 'topleft', 'topright', 'bottomleft', 'bottomright'; optional): determines the placement of tooltips
see https://github.com/react-component/tooltip#api
top/bottom{*} sets the _origin_ of the tooltip, so e.g. `topleft`
will in reality appear to be on the top right of the handle. Configuration for tooltips describing the current slider values}
\item{vertical}{Logical. If true, the slider will be vertical}
\item{verticalHeight}{Numeric. The height, in px, of the slider if it is vertical.}
\item{updatemode}{A value equal to: 'mouseup', 'drag'. Determines when the component should update its `value`
property. If `mouseup` (the default) then the slider
will only trigger its value when the user has finished
dragging the slider. If `drag`, then the slider will
update its value continuously as it is being dragged.
Note that for the latter case, the `drag_value`
property could be used instead.}
\item{loading_state}{Lists containing elements 'is_loading', 'prop_name', 'component_name'.
those elements have the following types:
- is_loading (logical; optional): determines if the component is loading or not
- prop_name (character; optional): holds which property is loading
- component_name (character; optional): holds the name of the component that is loading. Object that holds the loading state object coming from dash-renderer}
\item{persistence}{Logical | character | numeric. Used to allow user interactions in this component to be persisted when
the component - or the page - is refreshed. If `persisted` is truthy and
hasn't changed from its previous value, a `value` that the user has
changed while using the app will keep that change, as long as
the new `value` also matches what was given originally.
Used in conjunction with `persistence_type`.}
\item{persisted_props}{List of a value equal to: 'value's. Properties whose user interactions will persist after refreshing the
component or the page. Since only `value` is allowed this prop can
normally be ignored.}
\item{persistence_type}{A value equal to: 'local', 'session', 'memory'. Where persisted user changes will be stored:
memory: only kept in memory, reset on page refresh.
local: window.localStorage, data is kept after the browser quit.
session: window.sessionStorage, data is cleared once the browser quit.}
}
\value{named list of JSON elements corresponding to React.js properties and their values}
\examples{
if (interactive()) {
library(dash)
app <- Dash$new()
app$layout(
htmlDiv(
dccRangeSlider(
count = 1,
min = -5,
max = 10,
step = 0.5,
value = list(-3, 7),
marks = as.list(
setNames(-5:10, as.character(-5:10))
)
)
)
)
app$run_server()
}
}