similar to: par(lty = "1") -- lty storage-etc bug (PR#584)

Displaying 20 results from an estimated 500 matches similar to: "par(lty = "1") -- lty storage-etc bug (PR#584)"

2000 Jun 22
2
Postscript Legends (or not)
I discovered a little problem when using the Windows NT release of R 1.0.1, and it's still there in R 1.1.0. The boiled down version is this: I want to draw the following plot and put it into a Postscript file: x <- c(1,2,3,4); y1 <- c(1,2,3,4); y2 <- c(2,2,2,2) Fred <- c(1,2) postscript(file="d:/Bob/Papers/IFM/try2.ps") plot(x,y1, type="l")
1997 Jul 30
0
R-alpha: more on line types
forgot to fix psx11.c and devPicTeX.c while I was at it (devPicTeX.c doesn't seem to change the color). Should psx11.c be devpsx11.c? Diffs: *** psx11.c.orig Wed Jul 30 10:08:48 1997 --- psx11.c Wed Jul 30 10:09:10 1997 *************** *** 293,298 **** --- 293,299 ---- } if(fg != NA_INTEGER) { psx11_SetColor(fg); + psx11_SetLinetype(GP->lty); PostScriptOpenRectangle(psfp,
2000 Aug 16
1
Multiple pages with postscript() (PR#635)
Version: platform = i686-pc-linux-gnu arch = i686 os = linux-gnu system = i686, linux-gnu status = major = 1 minor = 1.0 year = 2000 month = June day = 15 language = R Search Path: .GlobalEnv, Autoloads, package:base The function will produce a three page file, but only the first one has the lwd parameter set. The other pages have reverted to lwd = 1. I've tried setting the
1997 Jul 30
0
R-alpha: line types
Responding to my own post, after some hacking: To fix the behavior of the following test code (the rect()s inherit the lty set by the previous abline())-- x _ (1:100)/10 plot(x,sin(x)) abline(h=0,lty=2,col="red") rect(1,0,2,0.5) abline(v=2) rect(3,0,4,0.5) Here are some diffs (now all I have to do is wade through and get lwd working properly ...) *** devX11.c.orig Tue Jul 29
2000 Feb 07
4
Segmentation fault, devPS.c, 0.99.0 (PR#413)
Full_Name: Roger Bivand Version: 0.99.0 OS: RH Linux 6.1 Submission from: (NULL) (158.37.60.152) I am working on an interface between R and the GRASS geographical information system, written in R, with no dynamically loaded code. I have written full examples, and tested then under R 0.90.1, both by entering example() for each function and R CMD check, both of which worked without problem. Under
2010 Oct 10
2
Line Type Specification: lty="<on><off>" but lty="<off><on>"?
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
2011 Apr 21
3
line type lty
Hi All, Does somebody know how to know the detail of the line types? For example, lty = 1, means what kind of line?, lty = 2, means what kind of line? Thanks. HXD [[alternative HTML version deleted]]
1999 Mar 10
0
lines/lty
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
2001 Jul 20
0
problem with printing lines with lty
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
1997 Jul 29
0
R-alpha: more graphics: lwd, persistent lty settings
[ 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
1999 Jul 17
0
Use of lwd = 0, lty = 2 in segments. (PR#230)
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
2003 Mar 12
1
plot() with type="s" and lty=2 (PR#2630)
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
2007 Nov 08
1
Mixing lty specifications in legend
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
2010 Feb 19
1
lty dots pdf issue
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
2011 Nov 14
2
arrow egdes and lty
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 --
2005 Dec 16
2
dendrogram branches with different lty
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)
1999 Mar 10
1
lty=2
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
2001 Feb 01
1
postscript and lty
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,
2003 May 21
1
axis() default values for "lty", "lwd", and "col"
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
2009 Oct 08
2
lattice: passing multiple lty values to the key/legend
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: #____________________________