gfile {gWidgets2} | R Documentation

## dialog for file and directory selection

### Description

dialog for file and directory selection

generic for toolkit dispatch

Basically an entry box instance with a button to initiate `gfile`.

generic for toolkit dispatch

### Usage

    gfile(text = "", type = c("open", "save", "selectdir"),
      initial.filename = NULL, initial.dir = getwd(), filter = list(),
      multi = FALSE, ..., toolkit = guiToolkit())

    .gfile(toolkit, text = "", type = c("open", "save", "selectdir"),
      initial.filename = NULL, initial.dir = getwd(), filter = list(),
      multi = FALSE, ...)

    gfilebrowse(text = "Select a file...", type = c("open", "save",
      "selectdir"), initial.filename = NULL, initial.dir = getwd(),
      filter = list(), quote = TRUE, handler = NULL, action = NULL,
      container = NULL, ..., toolkit = guiToolkit())

    .gfilebrowse(toolkit, text = "Select a file...", type = c("open", "save",
      "selectdir"), initial.filename = NULL, initial.dir = getwd(),
      filter = list(), quote = TRUE, handler = NULL, action = NULL,
      container = NULL, ...)

### Arguments

`text` | initial text
`type` | type of browser: to open a file, to save a file or to select a directory
`initial.filename` | Suggested file name
`initial.dir` | initial directory. If a filename is given, and is not an absolute name, this will be prepended. If filename given initial directory will be taken from that.
- `filter` | A filter specifiation. This can be a named character vector of file extensions or something toolkit specific. Here are some examples: characterc("csv"="csv","txt"="txt") RGtk2 Something like
      list("All files" = list(patterns = c("*")),
           "R files" = list(patterns = c("*.R", "*.Rdata")),
           "text files" = list(mime.types = c("text/plain"))
          )
tcltk Qt
`multi` | Logical. Allow multiple files to be selected?
`...` | 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`.
`quote` | quote output
`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.)

### Value

returns filename(s) or `character(0)` if no selection.

Returns an object of class `gFilebrowse`. This should inherit the methods of `gedit` instances.

[Package gWidgets2 version 1.0-8 Index]