> use
>
> par(mfrow=c(2,2), cex = 1)
This does work as written. But when I first checked single-call setting, an
mfrow change to cex in the same call superseded cex=1; hence my suggestion to
use separate calls to par().
Further checking confirms that the result of a call to par is dependent on
argument specification order in the call:
par(mfrow=c(2,2), cex = 1)
par("cex")
# 1
par(cex=1, mfrow=c(2,2))
par("cex")
# 0.83
This obviously isn't a problem, though as an aside I didn't immediately find
any comment on the effect of argument order in ?par. It just means you have to
be careful exactly what you specify.
It may also mean that for future-proofing against possible changes in par
execution order, you might want to use separate calls anyway.
Steve Ellison
*******************************************************************
This email and any attachments are confidential. Any use...{{dropped:8}}
______________________________________________
R-help@r-project.org mailing list -- To UNSUBSCRIBE and more, see
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.
