From S.Ellison at lgc.co.uk  Tue Jun 26 15:02:10 2007
From: S.Ellison at lgc.co.uk (S.Ellison at lgc.co.uk)
Date: Tue, 26 Jun 2007 15:02:10 +0200 (CEST)
Subject: [Rd] boxplot and bxp do not respect xlim by default (PR#9756)
Message-ID: <20070626130210.22BD56595A@slim.kubism.ku.dk>

What is mystifying is that the issue was not present in previous versions, =
so appropriate code already existed.

However, I agree that there seem to be a couple of additional issues that =
I had missed. =20

I am perfectly happy to look at this again myself, though, and provide =
extended code; would that help?

S

> This retains the current defaults for xlim with at unspecified but =
allows
> explicit specification of xlim. (which is the grouping level axis =
whether
> horizontal or vertical).

But it fails in a few other cases:  if the user sets the widths, this=20
doesn't respect that setting; if the user specifies the location of one=20
boxplot (so length(at) =3D=3D 1) it fails when it tries to access at[2].

This is a somewhat tricky problem, that needs more careful thought than=20
I have time for right now, so I'll leave it for someone else (or for=20
myself in a less busy future, which may exist in some alternate universe).

What I'd suggest you do in the short term is simply to set up the plot=20
axes the way you want before calling bxp, then call it with add=3DTRUE.

Duncan Murdoch


=
*******************************************************************=0D=0A=
This email and any attachments are confidential. Any use, co...{{dropped}}



[Rd] boxplot and bxp do not respect xlim by default (PR#9756)
S.Ellison at lgc.co.uk