gWidgets2: gspinbutton – R documentation

Become an expert in R — Interactive courses, Cheat Sheets, certificates and more!

gspinbutton

Spinbutton constructor

Description

A spinbutton allows the user to select from a pre-selected range of numbers. Similar to a slider, but with more precision, but slower to adjust. The basic arguments mirror that of seq.int.

generic for toolkit dispatch

Usage

gspinbutton(from = 0, to = 10, by = 1, length.out = NULL,
  along.with = NULL, value = from, digits = 0, handler = NULL,
  action = NULL, container = NULL, ..., toolkit = guiToolkit())

.gspinbutton(toolkit, from = 0, to = 10, by = 1, value = from,
  digits = 0, handler = NULL, action = NULL, container = NULL, ...)

Arguments

`from`	from value
`to`	to value
`by`	step length
`length.out`	number of steps. Only one of `by` or `length.out` is used.
`along.with`	Take from
`value`	initial value
`digits`	number of digits to display, should the toolkit support it
`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 `addHandlerChanged` or at construction time. Handlers are functions whose first argument, `h` in the documentation, is a list with atleast two components `obj`, referring to the object emitting the signal and `action`, which passes in user-specified data to parameterize the function call. Handlers may also be added via `addHandlerXXX` methods for the widgets, where `XXX` indicates the signal, with a default signal mapped to `addHandlerChanged` (cf. `addHandler` for a listing). These methods pass back a handler ID that can be used with `blockHandler` and `unblockHandler` to suppress temporarily the calling of the handler.
`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 `add` method of the parent container. Examples of values are `expand`, `fill`, and `anchor`, although they're not always supported by a given widget. For more details see add. Occasionally the variable arguments feature has been used to sneak in hidden arguments to toolkit implementations. For example, when using a widget as a menubar object one can specify a parent argument to pass in parent information, similar to how the argument is used with gaction and the dialogs.
`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 `guiToolkit`.

Examples

if(interactive()) {
  ## a range widget uses either a slider or a linked spinbutton to select a value
  w <- gwindow("Range widget", visible=FALSE)
  g <- ggroup(cont=w, horizontal=TRUE)
  sl <- gslider(from=0, to=100, by=1, value=0, cont=g, expand=TRUE, fill="both")
  sp <- gspinbutton(from=0, to=100, by=1, value=0, cont=g)

  ## Two ways to do this:
  ##  addHandlerChanged(sl, function(...) svalue(sp) <- svalue(sl))
  ##  addHandlerChanged(sp, function(...) svalue(sl) <- svalue(sp))

  f <- function(h, ...) svalue(h$action) <- svalue(h$obj)
  addHandlerChanged(sl, f, action=sp)
  addHandlerChanged(sp, f, action=sl)
  
  visible(w) <- TRUE
}

gWidgets2

Rewrite of gWidgets API for Simplified GUI Construction

v1.0-8

GPL (>= 3)

Authors

John Verzani

Initial release