?par documents this behavior. I think if you just initially large cex by the appropriate amount, that might compensate for it, but I haven't tested this (I use lattice and grid graphics). Otherwise, as suggested in ?par, consider ?layout.
Cheers, Bert On Fri, Sep 13, 2013 at 9:51 AM, Jannis <bt_jan...@yahoo.de> wrote: > Dear R users, > > > if I use par(mfrow=c(3,3)), R automatically changes the value of cex and > even setting cex=1 in the same par() call does not seem to prevent this. > Even though such behavior may be helpful an many cases, I am wondering > whether there is a easy way to switch this off (short of setting cex to a > value that would be 1 if modified by mfrow). > > In the end my desire to have the software do what I tell it to do and not > what its programmers think I would want to do was one of the reasons to > move away to R from (in)famous Excel ;-). > > Cheers > Jannis > > ______________________________**________________ > R-help@r-project.org mailing list > https://stat.ethz.ch/mailman/**listinfo/r-help<https://stat.ethz.ch/mailman/listinfo/r-help> > PLEASE do read the posting guide http://www.R-project.org/** > posting-guide.html <http://www.R-project.org/posting-guide.html> > and provide commented, minimal, self-contained, reproducible code. > -- Bert Gunter Genentech Nonclinical Biostatistics Internal Contact Info: Phone: 467-7374 Website: http://pharmadevelopment.roche.com/index/pdb/pdb-functional-groups/pdb-biostatistics/pdb-ncb-home.htm [[alternative HTML version deleted]] ______________________________________________ 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.
