search for: r_default_device

Setting enviroment variable R_DEFAULT_DEVICE causes an error. The patch below fixes this. I guess the same goes for R_INTERACTIVE_DEVICE. --- R-2.7.0/src/library/grDevices/R/zzz.R 2008-04-27 13:49:11.000000000 +0200 +++ R-2.7.0/src/library/grDevices/R/zzz.R.new 2008-04-27 13:59:37.000000000 +0200 @@ -22,7 +22,7 @@ extras <...

When invoking dev.new() on my Mac OS X 10.4.11, I get an X11 window instead of quartz which I feel more desirable. So I'd like to set the default device to quartz. However I'm confused because of the following: > Sys.getenv("R_DEFAULT_DEVICE") R_DEFAULT_DEVICE "quartz" > getOption("device") [1] "X11" What's going on? Also is file Renviron under /Library/Frameworks/R.framework/Resources/ etc/ppc/ the one I should modify if I want to change some environment variables? But I don't...

...systems. > > dev.new() add a new argument 'noRStudioGD' in R 3.1.1.? Thank you. > It works for me when using RStudio on Windows, but on the unix > system it opens a pdf device instead of an interactive device when > using an interactive RStudio session (with R_DEFAULT_DEVICE and > R_INTERACIVE_DEVICE not set). > > Do other unix RStudio users see this behavior? > > It appears that the relevant line of dev.new (and in zzz.R): > > ? ? else if (nzchar(dsp) && .Platform$GUI %in% c("X11", "Tk")) > ? ?...

...latform-specific plot device on *unix* systems. dev.new() add a new argument 'noRStudioGD' in R 3.1.1. Thank you. It works for me when using RStudio on Windows, but on the unix system it opens a pdf device instead of an interactive device when using an interactive RStudio session (with R_DEFAULT_DEVICE and R_INTERACIVE_DEVICE not set). Do other unix RStudio users see this behavior? It appears that the relevant line of dev.new (and in zzz.R): else if (nzchar(dsp) && .Platform$GUI %in% c("X11", "Tk")) X11 else defdev but when I step through in...

...me from RStudio. They could provide a way for a user to indicate that they sometimes don't want to use the RStudio graphics device (e.g. an option setting), and your package could set and restore this option around your dev.new() call. The other seems to be for your package to temporarily set R_DEFAULT_DEVICE if the user doesn't already have it set, and use noRStudioGD=TRUE. The disadvantage of this is that you need to do all the platform-based decision making. Duncan > > On 09/25/2015 08:31 PM, Ott Toomet wrote: >> Can you describe your problem a bit more? >> >> * What ki...

...se they add it as a feature in the rstudioapi. However, since the noRstudioGD option now exists in R, I'd think it should behave consistently across platforms? Opening pdf on one and interactive on another seems odd. > > The other seems to be for your package to temporarily set > R_DEFAULT_DEVICE if the user doesn't already have it set, and use > noRStudioGD=TRUE. The disadvantage of this is that you need to do all > the platform-based decision making. Great idea, I'll employ this workaround for now. Thanks! best, -skye

...device on *unix* systems. > > dev.new() add a new argument 'noRStudioGD' in R 3.1.1. Thank you. It > works for me when using RStudio on Windows, but on the unix system it opens > a pdf device instead of an interactive device when using an interactive > RStudio session (with R_DEFAULT_DEVICE and R_INTERACIVE_DEVICE not set). > > Do other unix RStudio users see this behavior? > > It appears that the relevant line of dev.new (and in zzz.R): > > else if (nzchar(dsp) && .Platform$GUI %in% c("X11", "Tk")) > X11 > else de...

...ther than on the local machine. I think the RStudio people would have to make sure this worked, and if they're doing that, wouldn't it be easier for them to provide the option themselves? Duncan Murdoch >> >> The other seems to be for your package to temporarily set >> R_DEFAULT_DEVICE if the user doesn't already have it set, and use >> noRStudioGD=TRUE. The disadvantage of this is that you need to do all >> the platform-based decision making. > > Great idea, I'll employ this workaround for now. Thanks! > > best, > -skye > > ________...

Hi, haven't been here for a while, but everyone one was always so helpful I thought I would ask you another really basic question. I'm running R2.9.1 in Ubuntu8.04 on a netbook (maxed out on memory etc so I don't think that's a problem - wth it's a Dell Mini 9" with that lpia non-architecture you told me about). Anyway, some of the graphics functions/parameters are

> The problem is that the device chosen by dev.new() depends on the GUI. > You can see the code that does this in grDevices:::.onLoad. So in fact > with noRstudioGD=TRUE, the decision is identical to what it is in R: > you only get X11 if your GUI is X11 or Tk, you get pdf otherwise. > It's pretty common to use R on a machine where X11 won't work, so this > makes sense.

...the Depends field in a DESCRIPTION file: only the first mention will be used in R < 2.7.0. GRAPHICS CHANGES o The default graphics devices in interactive and non-interactive sessions are now configurable via environment variables R_INTERACTIVE_DEVICE and R_DEFAULT_DEVICE respectively. o New function dev.new() to launch a new copy of the default graphics device (and taking care if it is "pdf" or "postscript" not to trample on the file of an already running copy). o dev.copy2eps() uses dev.displaylist(...

...the Depends field in a DESCRIPTION file: only the first mention will be used in R < 2.7.0. GRAPHICS CHANGES o The default graphics devices in interactive and non-interactive sessions are now configurable via environment variables R_INTERACTIVE_DEVICE and R_DEFAULT_DEVICE respectively. o New function dev.new() to launch a new copy of the default graphics device (and taking care if it is "pdf" or "postscript" not to trample on the file of an already running copy). o dev.copy2eps() uses dev.displaylist(...