On 21/05/2013 21:24, Bert Gunter wrote:
At the risk of misunderstanding... (inline)
On Tue, May 21, 2013 at 12:17 PM, Milan Bouchet-Valat <nalimi...@club.fr> wrote:
Le mardi 21 mai 2013 à 08:17 -0700, Jeff Newmiller a écrit :
That is like complaining that your hammer does not fit these
newfangled Philips screws.
These are different tools. Do not expect them to interoperate.
I understand that Lattice and ggplot2 do not use settings from par().
I'm fine with this, as these packages are different from base graphics
and have they own equivalent to tweak settings.
What I do not understand is that one argument passed to output devices,
which are _not_ provided by package graphics, is ignored by these two
packages. Lattice and ggplot2 do not provide an alternative output
system,
False, I believe, depending on what you mean by "output system". They
both use grid graphics, not base graphics and with lattice, anyway,
Indeed. The issue is a design difference between the base and grid
graphics subsystems. See the 'R Internals' manual for more details.
you require a lattice specific device call:
?trellis.device
## this is called automatically when plotting if such a device is not
open already.
Of course, everything works in R, so if that is what you mean by
output system ...
Cheers,
Bert
so they indeed already "interoperate" with existing output
devices to a certain extent; though they require you to set a separate
option in at least one case. Since package graphics has a way to hook
into the device parameters, maybe Lattice and ggplot2 could have a way
to adapt they default settings to respect them.
And BTW, please provide quotations where I am actually complaining. I'm
willing to work on improving things where possible. Please do not
consider any remark or question as a rant -- except if you want to scare
potential contributors away, of course.
Regards
---------------------------------------------------------------------------
Jeff Newmiller The ..... ..... Go Live...
DCN:<jdnew...@dcn.davis.ca.us> Basics: ##.#. ##.#. Live Go...
Live: OO#.. Dead: OO#.. Playing
Research Engineer (Solar/Batteries O.O#. #.O#. with
/Software/Embedded Controllers) .OO#. .OO#. rocks...1k
---------------------------------------------------------------------------
Sent from my phone. Please excuse my brevity.
Milan Bouchet-Valat <nalimi...@club.fr> wrote:
Le mardi 21 mai 2013 à 23:30 +1000, Duncan Mackay a écrit :
Hi
See par.settings in xyplot
Things are also controlled by
trellis.par.get()
to see values
trellis.par.set()
eg
xyplot(~Freq|Year, data = sheep2,
groups = farm,
par.settings = list(strip.background = list(col =
"transparent"),
axis.text = list(cex = 0.75),
par.xlab.text = list(cex = 0.80),
par.ylab.text = list(cex = 0.80)) ,
...)
HTH
Thanks, but that's not really my question. I've already found the way
to
change text size. What I'm wondering is whether something could be done
so that the pointsize argument that is passed to graphical devices has
an effect on Lattice and ggplot2 plots.
Regards
Duncan
Duncan Mackay
Department of Agronomy and Soil Science
University of New England
Armidale NSW 2351
Email: home: mac...@northnet.com.au
At 21:18 21/05/2013, you wrote:
Hi!
When inserting R plots into a document using odfWeave, I fought for
a
while to get Lattice plots use the same text size as base plots. I
eventually discovered that specifying a point size via e.g.
svg(pointsize=10) has no effect on Lattice plots. One needs to
adjust
the size manually via:
trellis.par.set(fontsize=list(text=10, points=8))
This is also developed for both Lattice and ggplot2 by this blog
post:
http://gforge.se/2013/03/exporting-plain-lattice-or-ggplot/
So I am wondering whether is a by-design limitation or whether this
could be improved. I find it very useful to be able to adapt text
size
to the output device instead of changing plotting parameters for
each
plotting system (especially when you change the resolution of PNG
output, or move from one output device to another).
Thanks in advance
______________________________________________
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.
______________________________________________
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.
______________________________________________
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.
______________________________________________
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.
--
Brian D. Ripley, rip...@stats.ox.ac.uk
Professor of Applied Statistics, http://www.stats.ox.ac.uk/~ripley/
University of Oxford, Tel: +44 1865 272861 (self)
1 South Parks Road, +44 1865 272866 (PA)
Oxford OX1 3TG, UK Fax: +44 1865 272595
______________________________________________
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.
