similar to: line type lty

Bug report, rather than R-help; This is at least since 1.0.0; didn't try even older versions .. Jim> Anon wrote: Anon> ...However, if I use Fred <- c(1,"33")... Is this a Anon> bug, or am I missing something? this made use it essentially something like par(lty = "1") Jim> This is an interesting problem. It boils down to the

Hi, Section 'Line Type Specification' in help(par) explains how you can do custom line types. For example: plot(NA, xlim=c(0,1), ylim=c(0,1)); abline(h=1/2, col="blue", lwd=2, lty="88"); will draw a dashed line segment where the line is composed of 8 units of "on" (blue color) and 8 units of "off" (transparent), then repeated. Now I'd like

Dear all, I'm using R 63.2 on windows NT, when I use > lines(x,y, lty=2) it produces a dashed line between the first pair of points and then reverts back to a solid line. It produces different colours perfectly ok, but it's not really a solution when the plot needs to be printed on a black and white printer. Has anyone got a fix? Simon Bond

I'm running R 1.3 on WinNT. When I plot lines with different linetypes e.g.: x<-matrix(rnorm(50),,5) plot(c(1,10),c(min(x),max(x)),type="n") for(i in 1:5) lines(x[,i],lty=i+1) legend( locator(1),legend=as.character(1:5),lty=2:6,ncol=2) I see the lines clearly on my screen. When printing them through R, I can see nearly no difference between them. When using another program

[ SunOS 4.1.3, R-0.50-a1; I'm mostly very pleased, I haven't been pounding on it as hard as some folks have ] par(lwd) seems to be a bit of a stub right now; I wouldn't necessarily expect it to do anything in the x11() driver (nor would I know how to fix it), but it would be nice in the postscript driver (e.g. for thick lines for things to be made into slides). I will try to

This may not be considered a bug but it is an incompatibility with S. There was a convention in S that the graphics parameter setting lwd = 0 is supposed to use the minimum possible line width on the device. It is not clear what that means on modern graphics devices but there is still code (like mine) that assumes something sensible happens with lwd = 0 It seems that R's postscript

Full_Name: Jerome Asselin Version: 1.6.2 OS: RedHat Linux 7.2 Submission from: (NULL) (142.103.173.179) In the following example, the line type lty=2 does not show properly across the entire line. x <- c(seq(0,.5,.001),seq(.6,1,.1)) y <- rep(1,length(x)) plot(x,y,type="s",lty=2) Sincerely, Jerome Asselin

Hi all I have a plot with lines, one specified as (say) lty=1, using standard line types, and another as (say) my own spec: lty="51". I can't get legend to display both. Toy example: > plot(1~1) > legend("topright", lty=c("51",1), legend=c("My own","Standard")) Error in segments(x1, y1, x2, y2, ...) : invalid line type: must be

I'm trying to redo an old plot with: > sessionInfo() R version 2.11.0 Under development (unstable) (2010-02-09 r51113) x86_64-apple-darwin9.8.0 When I do: pdf("lty.pdf",height = 6, width = 8) u <- 1:100/100 y <- matrix(rep(1:10,each = 100),100) matplot(u,y,lwd = 2,type ="l") dev.off() the line types that have dots are difficult to distinguish because the

Dear R developers, I want to draw an arrow in a figure with lty=2. The lty argument also affects the edge of the arrow, which is unfortunate. Feature or bug? Is there some way to draw an arrow with intact edge, still with lty=2? Example code: plot(1:10) arrows(4, 5, 6, 7, lty=2) Best wishes, Matthias --

Dear r-list, I am trying to visually seperate the two main clusters of a dendrogram. The idea is to use: 'edgePar=list(lty=3)' for 'dend1[[1]]' and 'edgePar=list(lty=1)' for 'dend1[[2]]' I have not found a way to solve this. Any suggestions? Patrick hc <- hclust(dist(USArrests), "ave") (dend1 <- as.dendrogram(hc)) par(mfrow=c(2,2)) plot(dend1)

On Wed, Mar 10, 1999 at 03:14:08PM +0000, Simon Bond wrote: > Dear all, > > I'm using R 63.2 on windows NT, when I use > > > lines(x,y, lty=2) > > it produces a dashed line between the first pair of points and then reverts > back to a solid line. It produces different colours perfectly ok, but it's > not really a solution when the plot needs to be printed

To the plot experts: when creating a plot containing different lines, each with a special line type, it may happen that the result of 'postscript()' is not readable by ghostview (which may not be an R error, thus not bug report ;-). This is the case when mixing lty as 0:6 and character or even when using lty as character only. Example: postscript("test.ps") plot(1:10,

Hi, I would like to recommend a minor modification in axis() which I believe can simplify the making of plots for publications. I am trying to define default values for par() in order to make labels bigger and lines thicker, so that the resulting plots look good when resized for publication purposes. I ran into the following problem... axis() does not use par() values as default for

hi all, It's not clear to me how (or if) I can pass multiple values for lty to a key in xyplot? I've tried: lines=list(lty=1:3), to no avail. Do I need to use something other than auto.key? (Deepayan, if you're out there, I have your book and must admit the answer isn't jumping out at me.) thanks in advance! Michael Folkes example code: #____________________________

I am confused by the behavior of the lines function when the lty argument is a vector. ?lines indicates that lty is a valid parameter, but says nothing else about it. ?plot.xy (which I think is what gets called) refers back to ?lines. ?plot.default says to see ?par. In ?par, about lty it says "Some functions such as lines accept a vector of values which are recycled. Other uses will take

I find, viewing the output with ghostview, that lty="2","3", or "4" gives the same dashed line. So basically you have choice of solid ("1") or dashed ("2","3","4"). If this is not implemented yet, maybe the docs should reflect it? Hmm now I tried plotting with both lty="2" and lty="3" for two separate

I'm having a problem with dotted lines (lty = 3) in the pdf output in documents generated with Sweave. In the displayed pdf, the dotted line does not show up and in the printed output, it is there but does not seem to respect the lwd argument, for example, it is very faint despite using lwd = 3. The dotted line is correct in a quartz window and if I save the Quartz window to a pdf and

The problem: =========== Once a dendrogram has a branch with both a line type AND a color (which is a character color), the plot.dendrogram function will not plot and return an error. I say this is a bug because (I believe), we would like a dendrogram to be able to use character colors, while also allowing control over line types. This e-mail includes an example, and what I think a solution

Hi List, is sth. like the following possible: legend(x,y,c("A","B","C"), lty=list(1,"42","11")) ? Or: is there a possibility to define a solid line using the "string" mode for lty? Thanks Marcus -- +-------- ><> ------------------------------------------- | E-Mail: eger.m at gmx.de (NEW) | marcus.eger at