help@r-project.org
> 主é¢: Re: [R] figure margins too large
>
> On 04/03/2014 04:32 PM, å¼ ä»¥æ¥ wrote:
> > Dear R experts,
> >
> >
> > I tried to plot some figures in R using postscript(), but it always shows
> > that the fugures margin is
On 03/04/2014 06:32, 张以春 wrote:
Dear R experts,
I tried to plot some figures in R using postscript(), but it always shows that
the fugures margin is too large. I don't know how to change it. The following
is my example:
postscript("All.eps",width=3.27,height=1.416,pointsize=12,family="Aria
On 04/03/2014 04:32 PM, 张以春 wrote:
Dear R experts,
I tried to plot some figures in R using postscript(), but it always shows that
the fugures margin is too large. I don't know how to change it. The following
is my example:
postscript("All.eps",width=3.27,height=1.416,pointsize=12,family="A
Dear R experts,
I tried to plot some figures in R using postscript(), but it always shows that
the fugures margin is too large. I don't know how to change it. The following
is my example:
> postscript("All.eps",width=3.27,height=1.416,pointsize=12,family="Arial")
>par(mar=c(5.1,4.5,4.1,2.1));
Hi Mark,
This comes down to the way that GTK+ allocates size to its widgets. The
allocation of a widget is initialized to have a width and height of 1. When
a child is added to a visible parent, the parent will execute its lay out
algorithm and allocate a certain amount of space to the widget. The
Thanks, Peter.
I did the following: restart R and run the same code with and without a minimal
system pause (Sys.sleep) after the line that adds the device to the GTK window.
Adding a pause will make it work, though I do not understand what is happening
here. Note the different settings of par(
Peter, thanks for the answer!
Indeed, it does work if I set par(mar=c(0,0,0,0)) but not when it is set to the
default values mar=c(5.1, 4.1, 4.1, 2.1).
The par settings returned in the example are the defaults, so no extraordinary
big mar settings or char size (see below).
Also, it does not matte
On Mar 8, 2012, at 20:27 , Mark Heckmann wrote:
> When using a gtkDrawingArea as a Cairo device I very often encounter the
> error: "figure margins too large"
> Even for the below "getting started" example from http://www.ggobi.org/rgtk2/
> this is the case.
>
>> win = gtkWindow()
>> da = gtk
When using a gtkDrawingArea as a Cairo device I very often encounter the error:
"figure margins too large"
Even for the below "getting started" example from http://www.ggobi.org/rgtk2/
this is the case.
> win = gtkWindow()
> da = gtkDrawingArea()
> win$add(da)
> asCairoDevice(da)
[1] TRUE
> plo
1. Use a sensible subject line
2. "Figure margins too large" means there is no space in the device to
plot the data, the margins take (almost) all the space already.
Uwe Ligges
On 26.01.2012 17:59, R. Michael Weylandt wrote:
I usually get that error when I'm replotting on a window/device th
Thank you Marc,
I have checked two versions following your suggestions and the default
setting of mar in both versions are same to each other as c(5,4,4,2)+0.1.
Besides, I dont change any default settings about the graphics devices.
For more info, following is my two sessions of R.
*1.*
R version
It is not the default setting for par("mar") that changed.
There are other device specific changes that occurred in 2.7.0,
including, for some devices (eg. pdf and bitmap), the default device
dimensions.
See the bullets in the NEWS file under "SIGNIFICANT USER-VISIBLE
CHANGES" and "GRAPHICS CHANG
on 09/09/2008 05:19 PM Hui-Yi Chu wrote:
> Hi everyone,
>
> I updated R from 2.6.2 to 2.7.2 recently but keep getting the error "figure
> margins too large" when plot pictures which never happened to me when using
> 2.6.2. After googling and searching the mailing list, I still have no idea
> how t
Hi everyone,
I updated R from 2.6.2 to 2.7.2 recently but keep getting the error "figure
margins too large" when plot pictures which never happened to me when using
2.6.2. After googling and searching the mailing list, I still have no idea
how to optimize it. One of my packages fixed bugs in 2.7.2
On May 6, 2008, at 10:30 PM, Prof Brian Ripley wrote:
What were H & W? For png() they are (by default) in pixels, for
pdf() in inches.
You haven't told us your OS, but I guess Mac OS. Please update to R
2.7.0: that offers you two new png() devices for higher-quality
plots, and various o
What were H & W? For png() they are (by default) in pixels, for pdf() in
inches.
You haven't told us your OS, but I guess Mac OS. Please update to R
2.7.0: that offers you two new png() devices for higher-quality plots, and
various other improvements. (If you want to use the cairo-based png
On May 6, 2008, at 10:43 PM, Alexy Khrabrov wrote:
I've used to have a script with a barplot command it in, preceded
by a png:
png(graph.file,height=H,width=W)
barplot(t,names.arg=breaks[2:(length(t)+1)],tck=gridlines)
-- worked before R 2.6.2. When I tried it in R 2.6.2, which I have
for
I've used to have a script with a barplot command it in, preceded by a
png:
png(graph.file,height=H,width=W)
barplot(t,names.arg=breaks[2:(length(t)+1)],tck=gridlines)
-- worked before R 2.6.2. When I tried it in R 2.6.2, which I have
for a while but didn't run with that script, it complain
18 matches
Mail list logo
