ggraphics {gWidgets2} | R Documentation |
Constructor for an embeddable graphics device
Description
Some toolkits provide an embeddable graphics device. When this is the case, this widget provides same.
Usage
ggraphics(
width = dpi * 6,
height = dpi * 6,
dpi = 75,
ps = 12,
handler = NULL,
action = NULL,
container = NULL,
...,
toolkit = guiToolkit()
)
.ggraphics(
toolkit,
width = dpi * 6,
height = dpi * 6,
dpi = 75,
ps = 12,
handler = NULL,
action = NULL,
container = NULL,
...
)
Arguments
width |
width of device (pixels) |
height |
hieght of widget (pixels) |
dpi |
dots per inch |
ps |
pointsize |
handler |
A handler assigned to the default change
signal. Handlers are called when some event triggers a widget to
emit a signal. For each widget some default signal is assumed, and
handlers may be assigned to that through Handlers may also be added via |
action |
User supplied data passed to the handler when it is called |
container |
A parent container. When a widget is created it can be incorporated into the widget heirarchy by passing in a parent container at construction time. (For some toolkits this is not optional, e.g. gWidgets2tcltk or gWidgets2WWW2.) |
... |
These values are passed to the |
toolkit |
Each widget constructor is passed in the toolkit it
will use. This is typically done using the default, which will
lookup the toolkit through |
Examples
## Not run:
## This shows how to use the device within a notebook
w <- gwindow("notebook example")
nb <- gnotebook(cont=w)
devs <- lapply(1:5, function(i) ggraphics(cont=nb, label=as.character(i)))
addHandlerChanged(nb, handler=function(h,...) {
## Tricky part is svalue(h$obj) is not the new page number -- but old
## so we use the pageno component here
gg <- h$obj[h$pageno]
visible(gg) <- TRUE
})
## End(Not run)