Displaying 14 results from an estimated 14 matches for "setdashes".
Did you mean:
xsetdashes
2010 Dec 14
1
postscript failure manifests in plot.TukeyHSD
Hello R Developers,
Dear R-developers,
I ran some standard tests with currently (today morning) compiled R release
candidate in Linux R 2.12.1 RC (2010-12-13 r53843). Some of these tests used
plot.TukeyHSD function. This worked OK on the screen (X11 device), but
PostScript file could not be rendered. The following example had the problem
with me:
postscript(file="tukeyplot.ps")
2002 Mar 25
2
Extreme value distributions (Long.)
This may not actually be an R/Splus problem, but it started
off that way .....
===+===+===+===+===+===+===+===+===+===+===+===+===+===+===+===+===+===+===
Executive summary:
==================
Simulations involving extreme value distributions seem to ``work''
when the underlying distribution is exponential(1) or exponential(2)
== chi-squared_2, but NOT when the underlying distribution is
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
2009 Dec 11
2
incorrect linetype with pdf device (PR#14128)
Full_Name: baptiste augui?
Version: 2.10.1 RC (2009-12-06 r50690)
OS: Mac OSX 10.5
Submission from: (NULL) (90.25.215.172)
The following code, run with a vanilla R session, produces different visual
output for the two devices,
library(grid)
pdf("test-pdf.pdf")
grid.newpage()
grid.lines(gp=gpar(lty="13", lineend = "butt"))
dev.off()
png("test-png.png")
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,
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")
2005 Sep 03
1
Whole lotta stuff
...for converting ruby arrays into point arrays.
Added a typedef for wxDash
Corrected/expanded the typemap for GetTextExtent
Added GetMultiLineTextExtent prototype (there are some others missing I
didn''t add. I added this one because the typemap was so close to the other)
Added typemap for SetDashes
3) It''s very late (just flew out to the West Coast) and I''m not
thinking straight. But I seem to recall there was a problem I shelved
earlier today where appropriate ruby interfaces weren''t being created
for files we %import.
Roy
____________________________...
2003 May 30
0
Re: [R] Postscript query: plotting long vectors (PR#3132)
Don MacQueen <macq@llnl.gov> writes:
> When I run the example in R 1.6.2, and view it with gs, I get a good plot.
> When I run the example in R 1.7.0, and view it with gs, I get a bad plot.
> (run on the same host)
>
> My "bad plot" is as described by Stephen.
...
> (followed by ~200000 lines of the same type, with slowly changing values)
>
> In the
2003 May 29
4
Postscript query: plotting long vectors
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
2000 Jun 27
0
par(lty = "1") -- lty storage-etc bug (PR#584)
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
2006 Oct 20
0
[695] trunk/wxruby2/swig/classes/include/wxPen.h: Get/SetStipple not available on GTK
...() const;
</span><span class="cx"> bool Ok() const;
</span><span class="lines">@@ -31,7 +34,10 @@
</span><span class="cx"> void SetColour(int red , int green , int blue ) ;
</span><span class="cx"> void SetDashes(int n , wxDash* dashes ) ;
</span><span class="cx"> void SetJoin(int join_style ) ;
</span><del>- void SetStipple(wxBitmap* stipple ) ;
</del><ins>+// not available on GTK
+#if defined(__WXMSW__) || defined(__WXMAC__)
+ void SetStipple(const wxBi...
2002 Jun 05
6
mixing different modes of lty line type specification in legend() ?
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
1999 Mar 03
4
xfig device
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
2004 Sep 24
5
AW: How to improve the quality of curve/line plots?
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