From djsamperi at gmail.com  Mon Mar 31 18:56:51 2014
From: djsamperi at gmail.com (Dominick Samperi)
Date: Mon, 31 Mar 2014 12:56:51 -0400
Subject: [Rd] rgl question
In-Reply-To: <533938EA.30304@gmail.com>
References: <CADUbQ5iKuXw_A7R2-6JZk0GK99jEOr2eRBBy2_CdfmKAX2Aj7A@mail.gmail.com>
	<533938EA.30304@gmail.com>
Message-ID: <CADUbQ5juFZ0R2O-93kEFPfGF2U8O4n+YRZMeCs2z4i0j8JVA3g@mail.gmail.com>

Thanks for the comment. No, there were no such prior calls,
unless rgl.lines() itself sets lty to dashed?

Here is a simple session run under Windows:
library(rgl)
x <- 1:20
y <- 1:20
z <- 1:20
rgl.lines(x,y,z) # displays dashed line
lines3d(x,y,z)  # displays solid line

I'm using R 3.1.0 alpha

On Mon, Mar 31, 2014 at 5:44 AM, Duncan Murdoch
<murdoch.duncan at gmail.com> wrote:
> On 30/03/2014, 9:20 PM, Dominick Samperi wrote:
>>
>> Hello,
>>
>> If I call lines3d(x,y,z) I get lines connecting each point, but
>> when I call rgl.lines(x,y,z) I get dashed lines, and adding
>> something like type='l' leads to an error message. The
>> docs seem to suggest that rgl.lines() calls lines3d(), so
>> I would expect the result to be the same.
>>
>> Any tips would be appreciated.
>
>
> The difference is in how they use the material properties:  rgl.lines sets
> them permanently, lines3d restores the original value after the call.  So
> I'd guess your call to rgl.lines followed a call to another rgl.* function
> that set the lty property to dashed.
>
> Duncan Murdoch



[Rd] rgl question
Dominick Samperi