DOM node to bind.
DOM node label that corresponds to the slider.
Formats the payload of an action.
Original payload.
Modified payload.
Callback with changes to the slider value.
Value from a sliderToValue() transform.
Determine the name of the action that should be associated with the node.
The action name is determined from
the tag's data-action
, name
or id
attribute (in that order).
A HTML element.
Name of action or null.
Determine the name of the signal that should be listened to from the backend.
The signal name is determined from the data-signal
,
data-action
, name
or id
attribute (in that order.)
For all attributes apart from data-signal
, the value is wrapped in an
object like { data: value-of-attribute }
. The data-signal
value
can contain a :
which will be used to create an object as well. That means
that data-signal="data:myvalue"
gives the same result as data-action="myvalue"
.
A HTML element.
Name of a signal or null.
How a value should be represented. For example, this can add units or convert from radians to degrees.
Input value as it is stored in the backend.
Representation of a value.
Reads the value.
Set the value.
Transform a value from the HTML range element to a value that should be stored.
Value from HTML range element.
Value to store.
Transform a backend value to a slider value.
Value as stored in backend.
Value for the HTML range element.
Find all labels for slider elements.
Determine whether to skip this element.
This can be forced by adding a data-skipwire=true
attribute
to the HTML tag.
A HTML element.
Wire all sliders.
Generated using TypeDoc
Make all
<input[type='range']>
with an action name interactive.In
index.html
:<label for="samples">Samples:</label> <input type="range" id="samples" value="1000" min="100" max="10000" step="100" />
In
analysis.py
:@ databench.on def samples(self, value): """Sets the number of samples to generate per run.""" yield self.set_state(samples=value)