similar to: inconsistency/bug in recordPlot/replayPlot

>>>>> 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

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

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

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 have trouble understanding the R list object and how to add objects and get them out. I''m trying to collect snapshots with recordPlot and replay them. Got great help from everybody here yesterday on my histogram function, works fine to make the pictures: histomatic <- function (s1,s2,s3,var){ if (is.numeric (s2[[var]])) { par(mfrow=c(3,1)); rz <- range(s1[[var]],

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

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

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

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")),

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) >

Hi, In order to make a movie-like animation of different graphs with replayPlot inside a fast loop: is there a way to avoid the appearance of some white stripes/streaks between the different calls to replayPlot? thanks in advance Johan VH

I was wondering if there is something that can be done to improve error messages when replaying a recorded plot. For example a graphics device that is too small usually results in a helpful error message: png(height = 100) plot(1) # Error in plot.new() : figure margins too large dev.off() However when this happens when replaying a recorded plot, the error message is not so helpful. myplot

Hi This appears to be happening (at least) because cairo_pdf() delays initialising a Cairo surface until BM_NewPage(), rather than initiliasing a Cairo surface in BM_Open(), and replayPlot() triggers some activity (set clip region) on the device BEFORE a new page is started (so the pointer to the Cairo surface is null, so BOOM). Not sure yet whether to blame replayPlot() for not starting

Hi, I wonder if this is expected or I'm doing a wrong thing. pdf() dev.control('enable') library("grid") plot(1) grid.text("A") res = recordPlot() dev.off() cairo_pdf() replayPlot(res) dev.off() *** caught segfault *** address 0x4, cause 'memory not mapped' > sessionInfo() R version 3.3.2 (2016-10-31) Platform: x86_64-apple-darwin13.4.0 (64-bit)

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 <-

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

On 15/10/2023 12:05 p.m., Shu Fai Cheung wrote: > Let me clarify my question: > > plot.new() > polygon(c(.5, .5, .75, .8), c(.25, .3, .4, .5)) > > If the device is an on-screen device, can I check whether a particular area > has anything drawn on it, or, to be precise, whether the color of a > particular area has all pixels equal to the background color. That is, if >

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