search for: polypath

Hi Just to clarify, I think this IS a problem with grid.path() as well as polypath(). For the example you give, grid.path() diverts to drawing a polygon (because there is no 'id' specified), and the NAs in 'x' generate two separate polygons, which get drawn one on top of the other. The correct analogy to the polypath() example is ... x2 <- matrix(x[!is.na(...

Hi, I see different results in png() and pdf() for polypath() on Windows when using the "winding" rule ## overlapping, both clock-wise x <- cbind(c(.1, .1, .6, .6, NA, .4, .4, .9, .9), c(.1, .6, .6, .1, NA, .4, .9, .9, .4)) pfun <- function() { plot(x) polypath(x * 0.8 + 0.2, rule = "winding", col = "#BEBEBE80...

On Thu, 4 Aug 2016 at 17:53 Michael Sumner <mdsumner at gmail.com> wrote: > On Thu, 4 Aug 2016 at 11:17 Paul Murrell <paul at stat.auckland.ac.nz> wrote: > >> Hi >> >> Just to clarify, I think this IS a problem with grid.path() as well as >> polypath(). >> >> > Hi, oh dear - sorry about that > > I appreciate the deeper explanation, I knew about the id aspect in grid, > but just forgot in my haste. > > I'll be more careful with examples if I find any more clues. > > I've found a possibly related issue,...

On Thu, 4 Aug 2016 at 11:17 Paul Murrell <paul at stat.auckland.ac.nz> wrote: > Hi > > Just to clarify, I think this IS a problem with grid.path() as well as > polypath(). > > Hi, oh dear - sorry about that I appreciate the deeper explanation, I knew about the id aspect in grid, but just forgot in my haste. I'll be more careful with examples if I find any more clues. Cheers, Mike. > For the example you give, grid.path() diverts to drawing a polyg...

Hello, it's probably worth adding that this is not a problem with pathGrob, only polypath. This code is sufficient to demonstrate the problem in Windows. ## overlapping, both clock-wise x <- cbind(c(.1, .1, .6, .6, NA, .4, .4, .9, .9), c(.1, .6, .6, .1, NA, .4, .9, .9, .4)) ## only a problem on Windows windows() and png() plot(x);polypath(x, rule = "winding", co...

...) outline <- map("worldHires", plot=FALSE) # returns a list of x/y coords xrange <- range(outline$x, na.rm=TRUE) # get bounding box yrange <- range(outline$y, na.rm=TRUE) xbox <- xrange + c(-2, 2) ybox <- yrange + c(-2, 2) # create the grid path in the current device polypath(c(outline$x, NA, c(xbox, rev(xbox))), c(outline$y, NA, rep(ybox, each=2)), col="light blue", rule="evenodd") As you can see, the polypath is on both sides of the country outline. Any help is much appreciated. Louise [[alternative HTML version deleted]]

This question seemed to me to be more appropriate for r-devel than for r-help. My apologies if this is not the case. Recently I installed ``cairo'' on my lap-top so that I could make use of the (newish) polypath() function, with on-screen graphics. (The polypath() function does not work with X11(type="Xlib").) The installation went smoothly, X11(type="cairo") works just fine, and polypath() works just fine. However the default "type" for X11() remains "Xlib" rather...

...that text() in svg() gets saved as path, which is unacceptable for my purposes. (Interestingly, text() in cairo_pdf() gets saved as text.) Is there a way to save text as text in svg? And paths also is what I plot a lot. I know there is segments(), which plots disconnected segments, and things like polypath(), which create closed paths (and subpaths). These are all very useful, but is there a function to draw a multi-segment path without closing it? That is, without connecting the last vertex to the first one? Thanks! -------------- next part -------------- A non-text attachment was scrubbed... Name...

...fer overflow affects users of any version of tikzDevice. However, it only occurs when bold italic text is used in plots which is a fairly rare occurrence. Many thanks to Mikhail Titov for taking the time to file bug reports that led to the discovery of this issues. Additionally, the vignette and polypath() functions have been updated/added to support changes in R 2.12.0 and support for Solaris was improved. For more info on the tikzDevice, please visit us on GitHub: http://github.com/Sharpie/RTikZDevice The combined changelog for version 0.5.1 and 0.5.2 is as follows: --- ### Version: 0.5....

...fer overflow affects users of any version of tikzDevice. However, it only occurs when bold italic text is used in plots which is a fairly rare occurrence. Many thanks to Mikhail Titov for taking the time to file bug reports that led to the discovery of this issues. Additionally, the vignette and polypath() functions have been updated/added to support changes in R 2.12.0 and support for Solaris was improved. For more info on the tikzDevice, please visit us on GitHub: http://github.com/Sharpie/RTikZDevice The combined changelog for version 0.5.1 and 0.5.2 is as follows: --- ### Version: 0.5....

...is officially supported. Compared to the PdfTeX engine, XeTeX has native support for Unicode which we hope will make the package more useful for producing graphics that contain text in languages?outside?the ASCII symbol table. 0.6.0 also provides support for including raster imagry in graphics and polypath drawing which catches the `tikz()` graphics device up with recent developments in the R graphics engine. There have also been some significant changes under the hood. Our package has migrated to using Roxygen for function documentation---a move that was greatly facilitated by the Rd2roxygen packag...

...is officially supported. Compared to the PdfTeX engine, XeTeX has native support for Unicode which we hope will make the package more useful for producing graphics that contain text in languages?outside?the ASCII symbol table. 0.6.0 also provides support for including raster imagry in graphics and polypath drawing which catches the `tikz()` graphics device up with recent developments in the R graphics engine. There have also been some significant changes under the hood. Our package has migrated to using Roxygen for function documentation---a move that was greatly facilitated by the Rd2roxygen packag...

...gnificant issues, the next release of the tikzDevice should be version 0.6.0. This release is planned to contain new functionality drawn from one or both of the following development efforts: - Support for UTF8 plot text when tikzDevice is used with the XeTeX engine. - Support for the raster and polypath additions to the R graphics engine. --- ### Version: 0.5.3 --- #### Bug Fixes - R 2.12.x now throws a warning message when shell commands run via `system()` have non-zero exit conditions. The metric calculation runs LaTeX on a file containing an \@@end command. This causes a non zero ex...

...gnificant issues, the next release of the tikzDevice should be version 0.6.0. This release is planned to contain new functionality drawn from one or both of the following development efforts: - Support for UTF8 plot text when tikzDevice is used with the XeTeX engine. - Support for the raster and polypath additions to the R graphics engine. --- ### Version: 0.5.3 --- #### Bug Fixes - R 2.12.x now throws a warning message when shell commands run via `system()` have non-zero exit conditions. The metric calculation runs LaTeX on a file containing an \@@end command. This causes a non zero ex...

...mplemented (see for example the PicTeX and XFig devices in the 'grDevices' package). A full implementation of dev_Path() should be able to render paths that consist of multiple sub-paths which can be filled using either the even-odd rule or the non-zero winding rule (see the examples in polypath() from 'graphics' or grid.path() from 'grid'). Paul -- Dr Paul Murrell Department of Statistics The University of Auckland Private Bag 92019 Auckland New Zealand 64 9 3737599 x85392 paul at stat.auckland.ac.nz http://www.stat.auckland.ac.nz/~paul/

...ns with holes to the graphics engine. This is implemented for the pdf(), postscript(), x11(type="cairo"), windows(), and quartz() devices (and associated raster formats), but not for x11(type="Xlib") or xfig() or pictex(). The user-level interface is the polypath() function in graphics and grid.path() in grid. ? File NEWS is now generated at installation with a slightly different format: it will be in UTF-8 on platforms using UTF-8, and otherwise in ASCII. There is also a PDF version, NEWS.pdf, installed at the top-level of the...

...ns with holes to the graphics engine. This is implemented for the pdf(), postscript(), x11(type="cairo"), windows(), and quartz() devices (and associated raster formats), but not for x11(type="Xlib") or xfig() or pictex(). The user-level interface is the polypath() function in graphics and grid.path() in grid. ? File NEWS is now generated at installation with a slightly different format: it will be in UTF-8 on platforms using UTF-8, and otherwise in ASCII. There is also a PDF version, NEWS.pdf, installed at the top-level of the...