Hi
Gabor Grothendieck wrote:
On Jan 23, 2008 9:38 PM, Paul Murrell [EMAIL PROTECTED] wrote:
Hi
Gabor Grothendieck wrote:
Why does the seekViewport at the bottom give an error?
Because the viewport is popped after GRID.cellGrob.84 is drawn.
grid.ls() shows the viewport because it
Hi
hadley wickham wrote:
The problem (see also
https://stat.ethz.ch/pipermail/r-help/2008-January/151655.html) is that
cellGrobs (children of frame grobs) use their 'vp' component to store
the viewport that positions them within the parent frame. This means
that the viewport is pushed and
Hi
Gabor Grothendieck wrote:
Why does the seekViewport at the bottom give an error?
Because the viewport is popped after GRID.cellGrob.84 is drawn.
grid.ls() shows the viewport because it recurses down into the legend
frame grob. Compare your output with (grid-generated numbering differs)
On Jan 23, 2008 9:38 PM, Paul Murrell [EMAIL PROTECTED] wrote:
Hi
Gabor Grothendieck wrote:
Why does the seekViewport at the bottom give an error?
Because the viewport is popped after GRID.cellGrob.84 is drawn.
grid.ls() shows the viewport because it recurses down into the legend
frame
The problem (see also
https://stat.ethz.ch/pipermail/r-help/2008-January/151655.html) is that
cellGrobs (children of frame grobs) use their 'vp' component to store
the viewport that positions them within the parent frame. This means
that the viewport is pushed and then popped (as per normal
Why does the seekViewport at the bottom give an error?
xyplot(Sepal.Length ~ Sepal.Width, iris, group = Species, col = 11:13,
+ auto.key = TRUE)
grid.ls(view = TRUE)
ROOT
GRID.rect.89
plot1.toplevel.vp
plot1.xlab.vp
plot1.xlab
1
plot1.ylab.vp
plot1.ylab
1
