From simon.urbanek at r-project.org  Tue Feb  7 00:12:23 2006
From: simon.urbanek at r-project.org (Simon Urbanek)
Date: Mon, 6 Feb 2006 18:12:23 -0500
Subject: [Rd] invalid graphics state using dev.print
In-Reply-To: <02575270-8477-48E4-97AD-03BC127B0FBE@houston.rr.com>
References: <02575270-8477-48E4-97AD-03BC127B0FBE@houston.rr.com>
Message-ID: <24E8DC10-8C07-4E1A-93F6-E462CB1E96BB@r-project.org>

Paul,

On Feb 6, 2006, at 5:24 PM, Paul Roebuck wrote:

> Tried on R-Sig-Mac with no responses, but I need some kind of answer.
> [...]
> Does the following work on your system?

Interesting, no, it doesn't either. For png and pdf I use Quartz +  
quartz.save (it produces much nicer results) so I didn't really  
notice, but you're right. First I thought those graphics state issues  
are specific to the Quartz device, but you have proven that it's not.  
It's in fact not even Mac-specific - I have just reproduced it on a  
Linux box - that's why I'm moving this to R-devel.

Here is a small reproducible example:
x11()
plot(rnorm(10))
dev.print(png)

I'll try to have a look at it later today, but I can't promise anything.

Cheers,
Simon



[Rd] invalid graphics state using dev.print
Simon Urbanek