Re: [Rd] seekViewport error

2008-01-27 Thread Paul Murrell
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 viewp

Re: [Rd] seekViewport error

2008-01-24 Thread Paul Murrell
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 pu

Re: [Rd] seekViewport error

2008-01-23 Thread hadley wickham
> 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 nor

Re: [Rd] seekViewport error

2008-01-23 Thread Gabor Grothendieck
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 l

Re: [Rd] seekViewport error

2008-01-23 Thread Paul Murrell
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)