6 messages · Gabor Grothendieck, Hadley Wickham, Paul Murrell +1 more
The following: library(grid) grid.newpage() example(Grid) has the yaxis label partly cut off and the x axis label does not appear at all. Also ?grid.multipanel in that example brings up documentation for grid-internal but this would not seem to be internal if its part of an example. I am using:
R.version.string # Windows XP
[1] "R version 2.2.0, 2005-09-20"
I've also noticed the behaviour of grid.rect() has changed in 2.2.0. Before the fill defaulted to transparent, but now it defaults to white. Hadley
The following: library(grid) grid.newpage() example(Grid) has the yaxis label partly cut off and the x axis label does not appear at all. Also ?grid.multipanel in that example brings up documentation for grid-internal but this would not seem to be internal if its part of an example. I am using:
R.version.string # Windows XP
[1] "R version 2.2.0, 2005-09-20"
______________________________________________ R-devel at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Hi
> I've also noticed the behaviour of grid.rect() has changed in 2.2.0. > Before the fill defaulted to transparent, but now it defaults to > white. The initial value of the 'gp' settings for the ROOT grid viewport has changed in 2.2.0 (see grid/doc/changes.txt). Before it defaulted to transparent, but now it defaults to whatever the 'bg' is for the current device (on some, e.g., png() this is "white", though I'm not sure why right now) so on some devices something like grid.rect() behaves differently. If before you had something like ... <draw, draw, draw ...> # Now I think I'll draw a nice border around the outside grid.rect() ... you should either do ... # I'll draw a rectangle first in case there is a non-transparent # fill in effect; NOTE that if I was writing perfect grid code # I would always be aware that I might be being drawn in a viewport # that was defined by someone else who might have, for example, # defined a non-transparent fill, so it's not entirely # grid's fault that things suddenly aren't working as I planned grid.rect() <draw, draw, draw ...> ... or ... <draw, draw, draw ...> # Now I think I'll draw a nice border around the outside # AND I really want JUST the border; I have absolutely no # intention of filling this rectangle, no matter what the # current fill setting happens to be grid.rect(gp=gpar(fill="transparent")) Paul
> >>The following: >> >>library(grid) >>grid.newpage() >>example(Grid) >> >>has the yaxis label partly cut off and the x axis label does not appear at all. >>Also ?grid.multipanel in that example brings up documentation for >>grid-internal but this would not seem to be internal if its part of an example. >> >>I am using: >> >> >>>R.version.string # Windows XP >> >>[1] "R version 2.2.0, 2005-09-20" >> >>______________________________________________ >>R-devel at r-project.org mailing list >>https://stat.ethz.ch/mailman/listinfo/r-devel >> > > > ______________________________________________ > R-devel at r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-devel
Dr Paul Murrell Department of Statistics The University of Auckland Private Bag 92019 Auckland New Zealand 64 9 3737599 x85392 paul at stat.auckland.ac.nz http://www.stat.auckland.ac.nz/~paul/
Hi
The following: library(grid) grid.newpage() example(Grid) has the yaxis label partly cut off and the x axis label does not appear at all. Also ?grid.multipanel in that example brings up documentation for grid-internal but this would not seem to be internal if its part of an example.
grid.multipanel() is just a demo hack function, not intended for people to use for anything serious, just meant to provide an example of what can be done. It had some merit when grid was just a prototype package for people to play with. Now that grid is more mature I should probably just kill grid.multipanel(). Paul
Dr Paul Murrell Department of Statistics The University of Auckland Private Bag 92019 Auckland New Zealand 64 9 3737599 x85392 paul at stat.auckland.ac.nz http://www.stat.auckland.ac.nz/~paul/
hadley wickham wrote:
I've also noticed the behaviour of grid.rect() has changed in 2.2.0. Before the fill defaulted to transparent, but now it defaults to white.
The initial value of the 'gp' settings for the ROOT grid viewport has changed in 2.2.0 (see grid/doc/changes.txt). Before it defaulted to transparent, but now it defaults to whatever the 'bg' is for the current device (on some, e.g., png() this is "white", though I'm not sure why right now)
Because many (maybe even most) png viewers do not handle transparency correctly.
Brian D. Ripley, ripley at stats.ox.ac.uk Professor of Applied Statistics, http://www.stats.ox.ac.uk/~ripley/ University of Oxford, Tel: +44 1865 272861 (self) 1 South Parks Road, +44 1865 272866 (PA) Oxford OX1 3TG, UK Fax: +44 1865 272595
Hi Gabor Grothendieck wrote:
The following: library(grid) grid.newpage() example(Grid) has the yaxis label partly cut off and the x axis label does not appear at all. Also ?grid.multipanel in that example brings up documentation for grid-internal but this would not seem to be internal if its part of an example.
grid.multipanel() is just a demo hack function, not intended for people to use for anything serious, just meant to provide an example of what can be done. It had some merit when grid was just a prototype package for people to play with. Now that grid is more mature I should probably just kill grid.multipanel().
If you kill it I still think it would be a nice to provide a similar example. I am sorry that I missed knowing about it when initially trying to learn how to do layouts since it might have saved me some time. Maybe it can be incorporated into the example section of one of the help files or into a demo or even a vignette on grid.multipanel. Also note that grid.multipanel is used not only in Grid but also in: http://www.stat.auckland.ac.nz/~paul/grid/doc/rotated.pdf