Hello,

Without looking to much at your function pdfc(), it is obvious to me that the error comes not from what the function does or does not, but from not having dots '...' as a formal argument. Simply put, you can only use '...' inside a function if it's a formal argument to that function.

Try pdfc <- function (file = "Rplot.pdf", ...) and see what happens.

Hope this helps,

Rui Barradas

Em 08-10-2012 14:39, Christian Hoffmann escreveu:
Hi,

Iwrote 'pdfc' in analogy to 'lpr':

pdfc <- function (file = "Rplot.pdf") {
  current.device <- dev.cur()
  dev.off(dev.copy(device = pdf, file = file, ...))
  dev.set(current.device)
  print(paste(file, "generated."))
  }

lpr <- function (object, file = "Rplotlpr.ps", ...)
{
    if (missing(object)) {
        current.device <- dev.cur()
        dev.off(dev.copy(device = postscript, file = file, ...))
        dev.set(current.device)
        system(paste("lpr", file))
        print(paste(file, "printed."))
    }
    else {
        if (missing(file))
            file <- "Robjlpr.txt"
        sink(file)
        object <- as.character(substitute(object))
        print(get(object))
        sink()
        system(paste("lpr", file))
        print(paste(object, "printed."))
    }
}

Now, while

lpr()
[1] "Rplotlpr.ps printed."

is working almost fine (the plot window of Quartz-2 is not sized correctly, what would you suggest, Ray Brownrig \email{r...@mcs.vuw.ac.nz} ?),

with > pdfc()

I get

Error in dev.off(dev.copy(device = pdf, file = file, ...)) :
  '...' used in an incorrect context

I searched the Web, but found no hint how to avoid this error. So the culprit could be

device = pdf

On the other hand  executing

pdf()

generates the file

Rplotlpr.ps

but this very small and causes the Adobe Reader to say

This file is damaged and cannot be opened.


Thanks for help.

Chirsitan HOffmann


______________________________________________
R-help@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.

Reply via email to