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
|
\name{vertexControl}
\alias{vertexControl}
\title{
Set attributes of vertices
}
\description{
This is a function to produce actions in a web display. A
\code{\link{playwidget}} or Shiny
input control (e.g. a \code{\link[shiny]{sliderInput}} control)
sets a value which controls attributes of a selection of vertices.
}
\usage{
vertexControl(value = 0, values = NULL, vertices = 1, attributes,
objid = tagged3d(tag), tag,
param = seq_len(NROW(values)) - 1, interp = TRUE)
}
\arguments{
\item{value}{The value to use for input (typically \code{input$value}
in a Shiny app.) Not needed with \code{\link{playwidget}}.}
\item{values}{
A matrix of values, each row corresponding to an input value.
}
\item{vertices}{
Which vertices are being controlled? Specify \code{vertices} as a number from 1 to
the number of vertices in the \code{objid}.
}
\item{attributes}{A vector of attributes of a vertex,
from \code{c("x", "y", "z", "red", "green", "blue", "alpha", "nx", "ny", "nz",
"radii", "ox", "oy", "oz", "ts", "tt", "offset")}. See
Details.}
\item{objid}{
A single RGL object id.
}
\item{tag}{
An alternate way to specify \code{objid}.
}
\item{param}{
Parameter values corresponding to each row of \code{values}.
}
\item{interp}{
Whether to interpolate between rows of \code{values}.
}
}
\details{
This function
modifies attributes of vertices in a single
object. The \code{attributes} are properties of each vertex
in a scene; not all are applicable to all objects. In order,
they are: coordinates of the vertex \code{"x", "y", "z"}, color
of the vertex \code{"red", "green", "blue", "alpha"}, normal at the vertex
\code{"nx", "ny", "nz"}, radius of a sphere at the vertex
\code{"radius"}, origin within a texture \code{"ox", "oy"} and
perhaps \code{"oz"}, texture coordinates \code{"ts", "tt"}.
Planes are handled specially. The coefficients \code{a, b, c}
in the \code{\link{planes3d}} or \code{\link{clipplanes3d}}
specification are controlled
using \code{"nx", "ny", "nz"}, and \code{d} is handled as
\code{"offset"}. The \code{vertices} argument is interpreted
as the indices of the planes when these attributes are set.
If only one attribute of one vertex is specified, \code{values} may
be given as a vector and will be treated as a one-column matrix. Otherwise
\code{values} must be given as a matrix with \code{ncol(values) == max(length(vertices),
length(attributes))}. The \code{vertices} and \code{attributes} vectors will be recycled to the same length, and entries from column \code{j} of \code{values} will be applied to
vertex \code{vertices[j]}, attribute \code{attributes[j]}.
The \code{value} argument is translated into a row (or two rows if
\code{interp = TRUE}) of \code{values}
by finding its location in \code{param}.
}
\value{
A list of class \code{"rglControl"} of cleaned up parameter
values, to be used in an RGL widget.
}
\author{
Duncan Murdoch
}
\seealso{
The \HTMLVignette{WebGL}{}{User Interaction in WebGL} vignette
gives more details.
}
\examples{
saveopts <- options(rgl.useNULL = TRUE)
theta <- seq(0, 6*pi, length.out = 100)
xyz <- cbind(sin(theta), cos(theta), theta)
plot3d(xyz, type="l")
id <- spheres3d(xyz[1,,drop=FALSE], col="red")
widget <- rglwidget(width=500, height=300) \%>\%
playwidget(vertexControl(values=xyz,
attributes=c("x", "y", "z"),
objid = id, param=1:100),
start = 1, stop = 100, rate=10)
if (interactive() || in_pkgdown_example())
widget
options(saveopts)
}
|
