search for: setlinewidth

...currentdict end /Font4 exch definefont pop %%IncludeResource: font Symbol /Symbol findfont dup length dict begin {1 index /FID ne {def} {pop pop} ifelse} forall currentdict end /Font5 exch definefont pop %%EndProlog %%Page: 1 1 bp 56.97 589.42 557.32 741.98 cl 0.0000 0.0000 0.0000 rgb 0.75 setlinewidth [] 0 setdash 75.50 655.81 1.78 c p1 80.18 665.70 1.78 c p1 84.86 668.52 1.78 c p1 89.54 661.46 1.78 c p1 94.22 671.35 1.78 c p1 98.90 668.52 1.78 c p1 103.58 679.82 1.78 c p1 108.26 661.46 1.78 c p1 112.94 679.82 1.78 c p1 117.61 651.57 1.78 c p1 164.41 665.70 1.78 c p1 211.21 658.63 1.78 c p1 258....

...0, 51 and so on. Is that it? After a lot of experimentation, I found that a small change in the eps file can correct the output. If in the eps file produced above, you change the line /p2 { gsave bg fill grestore newpath } def with /p2 { bg gsave fill grestore stroke newpath } def and add 0.0001 setlinewidth two lines before the next p2 - i.e. before we start plotting the rectangles of the image: change: /bg { 1 0 0 setrgb } def 59.04 73.44 41.47 37.15 r p2 to: 0.0001 setlinewidth /bg { 1 0 0 setrgb } def 59.04 73.44 41.47 37.15 r p2 What this does is plot the outline of each rectangle in addition to...

...causes ghostscript to complain of an error. R> postscript("foo.ps") R> plot(1:10, 1:10, type = "n") R> abline(h = 5, lty = 2, lwd = 0) # works properly R> segments(1, 1, 1, 3, lty = 2, lwd = 0) # fails R> dev.off() The last part of the PostScript file is 0.75 setlinewidth [ 3.00 3.00] 0 setdash np 77.04 290.39 m 743.76 290.39 l o 0.00 setlinewidth [ 0.00 0.00] 0 setdash np 101.73 107.87 m 101.73 199.13 l It is the line "[ 0.00 0.00] 0 setdash" that causes the problems. The error message from Ghostscript is Error: /rangecheckAladdin Ghostscript: Unrecove...

...4, 3.5) -> ylim=c(2,4 ? 3,5), not to get a syntax error with the comma-decimal numbers? Workaround: I can set the value before I switch to "cz_CZ". -- And finally, how do I plot it to the postscript device with commas in labels (2,54), but with points in the postcsript commands (0.75 setlinewidth)? I can understand this is a problem of postscript language/interpreter which doesn't use locales, but R's postscript driver should know, it can't use commas in PS-command arguments. Workaround: I can use "pretty()" and "as.character()" with default "C" lo...

...o the same file generated with an older R in my Mac, I found one difference: $ diff -U2 oldtukeyplot.ps /Volumes/TIKKU/tukeyplot.ps --- oldtukeyplot.ps 2010-12-14 12:06:07.000000000 +0200 +++ /Volumes/TIKKU/tukeyplot.ps 2010-12-14 12:13:32.000000000 +0200 @@ -172,5 +172,5 @@ 0 setgray 0.00 setlinewidth -[ 3.00 5.00] 0 setdash +[ 0.00 0.00] 0 setdash np 660.06 91.44 m Editing the changed line to its old value "[ 3.00 5.00] 0 setdash" also fixed the problem both in Linux and in Mac. Evidently something has changed, and probably somewhere else than in plot.TukeyHSD (which hasn't cha...

...VEColor(parseInt(this.color.substr(1,2),16),parseInt(this.color.substr(3,2),16),parseInt(this.color.substr(5,2),16), opacity); }else{ color = new VEColor(0,255,0, opacity); } mpolyline = new VEShape(VEShapeType.Polygon, mpoints); mpolyline.SetLineColor(color); mpolyline.SetLineWidth(this.width || 1); mpolyline.HideIcon(); if(this.fillColor){ var fillColor = new VEColor(parseInt(this.fillColor.substr(1,2),16),parseInt(this.fillColor.substr(3,2),16),parseInt(this.fillColor.substr(5,2),16), opacity); mpolyline.SetFillColor(fillColor); } return mpo...

...oth line type and line width. In PostScript there are two separate calls. The following quick hack to SetLinetype() appears to work pretty well for X11, although there may be a better way to do it (logically, SetLinetype ought to take both lty and lwd as arguments, or there should be a separate SetLinewidth -- however, if there were two functions each would have to look at least briefly at the current settings so as not to screw them up): Before doing this in PostScript (where the width and type are set in separate calls), I'd like advice. Also, is there a particular reason that default line...

...cribed by Stephen. ... > (followed by ~200000 lines of the same type, with slowly changing values) > > In the "bad" postscript file, at about the same point in the file, is this: > %%EndProlog > %%Page: 1 1 > bp > 77.04 91.44 743.76 534.96 cl > 0 0 0 rgb > 0.75 setlinewidth > [] 0 setdash > np > 101.73 313.20 m > 0.00 0.01 l > 0.00 0.01 l > 0.00 0.01 l > 0.00 0.01 l > 0.00 0.01 l > (followed by ~200000 lines, including some like these) Confirmed on RedHat Linux 8.0. Filing as bug report. (An old version of Splus had a similar bug: If you wa...

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 have a query about the maximum length of vector that can be plotted in one go in a postscript driver. Try the following code (in 1.7.0; version details below): t <- seq(from=0, to=4*pi, length=200000) y <- sin(t) postscript(file="o.ps") plot(t, y, type="l") dev.off() If I view the postscript file o.ps in "gv", it takes many seconds before eventually

[[yet another discussion brought from R-core to R-devel]] >>>>> "RG" == Robert Gentleman <rgentlem@stat.auckland.ac.nz> writes: RG> Peter, there is some code for line types and widths in all the RG> drivers. With windows there is the well known limitation that you RG> can't have patterened lines with lwd larger than 1 (unless you

Hi, I am VERY interested in getting the xfig driver so that I can edit graphical output from R. Searching through the mail archives and reading documentation isn't helping. Is there or isn't there a working driver for this purpose. How can I get it? I tried looking at the development version of the tarballs, but I didn't find anything that looked promising in there. Also, does

Colors are real nice, but the publication I'm preparing these barplots for permits only black and white. The Splus plot options ``dbangle'' (or plain ``angle'') and ``density'' (as on p. 65 of MASS 1st ed.) don't seem to be available in R. Is there another way to do this? I'm running R 1.1.0 on Linux (intel). Thanks.

Thanks for the tip using a smoothing technique before plotiing in order to get a curve instead of a line connecting the observations. But that's not the solution for my main problem with the "unclean" line plot. In order to show my problem let's take this simple example: > xval <- c(1, 2, 3, 4, 5, 6, 7, 8) > yval <- c(10, 30, 40, 50, 70, 90, 100, 110) > plot