search for: devwindows

...to create any files that have the name "CON" before the file extension, i.e. all of the following fail: > pdf("CON.pdf") Error in pdf("CON.pdf") : unable to start device pdf > jpeg('CON.jpeg') Error in jpeg("CON.jpeg") : unable to start device devWindows > png('CON.png') Error in png("CON.png") : unable to start device devWindows > sink('CON.txt') Error in file(file, ifelse(append, "a", "w")) : unable to open connection > Any filename other than this works fine. > png('ICON....

doKeybd() gets called in CHelpKeyIn() and NHelpKeyIn() in library/grDevices/src/devWindows.c, where the call is encapsulated in an 'if (dd->gettingEvent)' block. So the only times this code ever calls doKeybd() is when gettingEvent is in fact set. Further, it's called in two locations in X11_eventHelper(), in modules/X11/devX11.c, where the state of gettingEvent seems to...

Hi, After I installed R in my computer, I have loaded package Faraway, but when I want to plot, it will show errors like below: *> x<-c(1,2) > y<-c(3,4) > plot(x,y) Error in windows() : unable to start device devWindows* I don't know why, please help me. Shuyan [[alternative HTML version deleted]]

...ot;C:/Temp/test.txt", width=17000, height=2000) plot(bb) dev.off() On my main computer, however, this doesn't work: > jpeg("C:/Temp/test.txt", width=17000, height=2000) Error in jpeg("C:/Temp/test.txt", width = 17000, height = 2000) : unable to start device devWindows In addition: Warning message: Unable to allocate bitmap This is a Windows XP Pro SP2 system, which is started with this chsort > R.version _ platform i386-pc-mingw32 arch i386 os mingw32 system i386, mingw32 status major...

...00, bg = "white") plot(z[1+i:((nrow(z)/4)+i),], type="l") dev.off()} return(dataframe)} and try to run: X(dataframe) I get this error message: Error in jpeg(filename = paste("test ", deparse(substitute(series)), i, : unable to start device devWindows In addition: Warning message: In jpeg(filename = paste("test ", deparse(substitute(series)), i, : Unable to open file 'test "dataframe" 0 .jpg' for writing Could anyone help me??? Thank you and have a nice day, Marcia -- View this message in context: http://www.nab...

...ersecting region when the "winding" fill rule is working correctly. The fill should be the same across the union of the square regions (this is what Cairo and PDF on Linux produce). Another data point: the problem is NOT just a matter of getting the rules round the wrong way in the devWindows.c; using rule="evenodd" produces the SAME result as using rule="winding". One more data point: this is not JUST a problem with polypath(). Creating a self-intersecting polygon and then drawing it, using polygon(), in windows(fillEvenOdd=FALSE) and windows(filleEvenOdd=TRUE...

...ould make it a more invasive patch to use. I'm also not certain it'd work the way I'd want it to, from looking at its internals. As far as I can tell, the prompt value is only used in two places; do_getGraphicsEvent() in src/main/gevents.c, and GA_eventHelper() in library/grDevices/src/devWindows.c. The latter has a sanity check for string-ness already, so making NA a possibility should be safe there, as well. That apparent lack of use elsewhere leads me to a question about the help file for getGraphicsEvent(). In it, the claim is made that 'prompt' is used to display a prompt text...

Hey all. As in general it's a bad idea to allow an event handler to generate an event, and as comments in the code seem to suggest this isn't the intention either, I was wondering about recursion in getGraphicsEvent(). In main/gevents.c, both doMouseEvent() and doKeybd() have the following line; dd->gettingEvent = FALSE; /* avoid recursive calls */ And they reset it to TRUE

...quot; fill rule is working correctly. The fill >> should be the same across the union of the square regions (this is what >> Cairo and PDF on Linux produce). >> >> Another data point: the problem is NOT just a matter of getting the >> rules round the wrong way in the devWindows.c; using rule="evenodd" >> produces the SAME result as using rule="winding". >> >> One more data point: this is not JUST a problem with polypath(). >> Creating a self-intersecting polygon and then drawing it, using >> polygon(), in windows(fillEve...

Oftentimes, I see graphs on the web that *look* like they've been produced by R, but I can never be sure. Or can I? I notice that PostScript files include a "%%%Creator: R Software" line, but do R graphics drivers encode any identifying information in GIF or PNG files more commonly used on the web? And of so, would such evidence necessarily be obliterated in post-processing (e.g

...n the "winding" fill rule is working correctly. The fill > should be the same across the union of the square regions (this is what > Cairo and PDF on Linux produce). > > Another data point: the problem is NOT just a matter of getting the > rules round the wrong way in the devWindows.c; using rule="evenodd" > produces the SAME result as using rule="winding". > > One more data point: this is not JUST a problem with polypath(). > Creating a self-intersecting polygon and then drawing it, using > polygon(), in windows(fillEvenOdd=FALSE) and wind...

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") polypath(x, rule =