similar to: recordPlot usage: add snaps to a list.

Hi What you are doing "wrong" is loading a recordedplot into the same session that it was created in. The saveRDS()/readRDS() works if you save in one R session and then read in a different R session. The assumption is that if you are still in the same session that created the recordedplot you still have the recordedplot (e.g., you can just do replayPlot(r) instead of

>>>>> Paul Murrell <paul at stat.auckland.ac.nz> >>>>> on Tue, 3 Apr 2018 09:41:56 +1200 writes: > Hi What you are doing "wrong" is loading a recordedplot > into the same session that it was created in. The > saveRDS()/readRDS() works if you save in one R session and > then read in a different R session. The

The documentation for recordPlot says the following: > As of R 3.3.0, it is possible (again) to replay a plot from another R session using, for example, saveRDS and readRDS. However, I haven't been able to save and restore a plot displaylist and have it work within the same R session, using R 3.4.3 or 3.3.3. Here's an example: # Save displaylist for a simple plot

Hi. Q. Is there a way to record a plot using grDevices::recordPlot() without opening an interactive (=visible GUI window) graphics device (not even for a flash of a second)? Related: help("recordPlot", package="grDevices") says: "These functions record and replay the displaylist of the current graphics device." Is the intention that recordPlot() should be able to

I am trying to save plots that I create using calls to windows() folowed by multiple calls to plot to place several plots on a page. I want to store the plots as variables to be able to recall them later. The documentation states: "Recorded plot histories are of class "SavedPlots". They have a print method, and a subset method. As the individual plots are of class

Hey all, I've run accross what seems to be a bug in the recordPlot/replayPlot functionality (or at least the lack of a feature which seems pretty reasonable to expect to be there) When drawing to a file-based graphics device (I tested with png()), the file resulting from calling replayPlot on a recordedplot object does not contain an identical image to that captured by the same graphics

I want to do a zoom with recordPlot(). I have problems with lists. (R-2.0.1 patched 2004-11-30 , various linux). I have problems with RecordPlot class structure. > plot(1:10) > saveP <- recordPlot() > dev.off() > sx <- saveP[[1]][[2]][[2]] > saveP[[1]][[2]][[2]] <- sx Error in "[[<-"(`*tmp*`, 1, value = list(list( .Primitive("plot.new")),

I think this is pretty certainly a bug, so I'm cc'ing this to r-bugs. -p Kaspar Pflugshaupt <pflugshaupt@geobot.umnw.ethz.ch> writes: > Hello, > > first, I'd like to congratulate the core team to the new R version 1.1. I > think it's a great update, with glimpses into an even greater future > (tcltk!). > > While playing around with the new functions

I use recordPlot() to save plots to disk that I render later to a variety of formats. This works fine for base R plots and ggplot2 plots, and also used to work for lattice plots. However somewhere in version 2.14 things stopped working for lattice plots. Here is an example: library(lattice); histogram(rnorm(100)); x <- recordPlot(); saveRDS(x, "myplot.rds"); y <-

Hello, first, I'd like to congratulate the core team to the new R version 1.1. I think it's a great update, with glimpses into an even greater future (tcltk!). While playing around with the new functions (on Win 95), I found the following: As the documentation states, when I generate a plot and save it with recordPlot, I can regenerate it by printing the variable: > plot(1:10) >

On Thu, Jun 22, 2000 at 05:01:32PM +0200, p.dalgaard@biostat.ku.dk wrote: > I think this is pretty certainly a bug, so I'm cc'ing this to r-bugs. > > -p > > Kaspar Pflugshaupt <pflugshaupt@geobot.umnw.ethz.ch> writes: > > As the documentation states, when I generate a plot and save it with > > recordPlot, I can regenerate it by printing the variable:

On Thu, Jun 22, 2000 at 05:01:32PM +0200, p.dalgaard@biostat.ku.dk wrote: > I think this is pretty certainly a bug, so I'm cc'ing this to r-bugs. > > -p > > Kaspar Pflugshaupt <pflugshaupt@geobot.umnw.ethz.ch> writes: > > As the documentation states, when I generate a plot and save it with > > recordPlot, I can regenerate it by printing the variable:

I have plots that were stored using recordPlot() in a fairly recent but pre-1.6.0 version of R that will not replayPlot() in R 1.6.0. The error message is Error in replayPlot(x) : invalid hex digit in color or lty The plots were stored in June (2002-6-14), each as an element of a list named 'rpl'. The version of R that was current then is what I used. At that time I was able to

I realize the R developers are probably overwhelmed and have little time for this, but the documentation really needs some serious reorganizaton. A good through description of basic variable types would help a lot, e.g. the difference between lists, arrays, matrices and frames. And, it appears there is some object-orientation to R, but it is not complete. I can't, for instance find a

Record plot which stores a plot to an internal R data structure and Replay Plot which replays the plot enables one to keep plots around and use them accross sessions at least until version 3. If you cannot restore old plots and treat them as data and save accross sessions, there is little reason for recordPlot. Either R needs to dispense with internal formats entirelly, a bad move in my opinion

In "An Introduction to R" (See R help menu), there is an example of a function 'open.account' that makes use of the lexical scope in R. I have a set of functions that can be used to output R tables and graphics into a single report document. (I am aware that several tools can do this already). While reorganizing my code, I realize that I can collect my functions in a list, in

This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01C344B0.28BC0750 Content-Type: text/plain; charset="windows-1252" Summary: Currently R provides > dev.control(displaylist='inhbit') to turn *off* the recording of graphics operations in a device, but there is no

R had an internal Plot format which could be saved in files and then reused. Just like one can save data.frames or lists of data which I routinely do could save plot which could be used for further elaboration and analysis. Thus you could modify a plot after you saved it. Matlab has a fig format which it uses for that purpose. The current version of R version 3 allows plots only to be used

Dear list, On Fedora 8 I downloaded the beta version of R via svn. make and make check-all worked fine, but make vignettes is failing with: make[1]: Entering directory `/home/gavin/R/2-7-patched/build/src/library' building/updating vignettes for package 'grid' ... processing 'displaylist.Snw' /usr/bin/texi2dvi: pdflatex exited with bad status, quitting. Error in

On 5/5/07, Prof Brian Ripley <ripley at stats.ox.ac.uk> wrote: [...] > You meam as in > > o dev.interactive() regards devices with the displaylist enabled > as interactive, and packages can register the names of their > devices as interactive via deviceIsInteractive(). > > ? Quick follow up: the displaylist based detection is working well, but