Thanks David. It turns out that I was in fact using a custom index.perm, but not on purpose. What happened was I used the "[" method on the trellis object ( lattice:::`[.trellis`), which of course is nothing but a short-cut for updating the index.perm. Lesson learned...
Regards, Ben On 08/27/2014 02:10 AM, David Winsemius wrote: > On Aug 26, 2014, at 3:25 PM, Benjamin Tyner wrote: > >> Hi, >> >> According to >> https://svn.r-project.org/R-packages/trunk/lattice/R/print.trellis.R, >> >> "[panel.number] is usually the same as, but can be different from >> packet.number" >> >> and I had been under the impression that as long as the user is not >> using a custom index.cond nor perm.cond, the panel.number would in fact >> be the same as the packet.number. >> >> However, I have recently come across a case where the two are *not* the >> same, even though I am not using a custom index.cond nor perm.cond. >> >> So my question is, what might be some other possible situations in which >> the two would be expected to differ? > The immediate hypothesis that leaps to mind is cases where there are multiple > pages. On each page I suspect the upper left numbering restarts with 1, but I > suspect the packet numbers are sequential increasing. >
______________________________________________ R-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.
