similar to: X11 Device Driver

On Sat, 16 Mar 2002 Edwin@balpol.tudelft.nl wrote: > Full_Name: Edwin > Version: 1.4.1 > OS: SunOS/Solaris > Submission from: (NULL) (130.161.1.115) > > > When selecting an X11 visual on Solaris 2.7 with > > X11(colortype="true") > > a PseudoColor visual is actually created. (verified with xwininfo) Note that the help page does *not* say that this

for some reason the following message seems not to have reached the list in the first try, at least I can't find it. my apologies if this is my fault: we are running R under Solaris with SunRay Terminals, which are set to 8 bit color to comply with some other software. In this configuration, X11() opens with colortype=true, i.e., it is not recognized that actually the display is only 8

I'm trying to create figures in PDF that use the 'gray' colormodel instead of the default 'RGB' model, by requirements of a publisher. My problem has to do with the fact that I'm not being able to get gray colors with this option on the pdf() driver. Here is a small example for problem replication: > R.version _ platform

ripley@stats.ox.ac.uk wrote: > > On Sat, 16 Mar 2002 Edwin@balpol.tudelft.nl wrote: > > > Full_Name: Edwin > > Version: 1.4.1 > > OS: SunOS/Solaris > > Submission from: (NULL) (130.161.1.115) > > > > > > When selecting an X11 visual on Solaris 2.7 with > > > > X11(colortype="true") > > > > a PseudoColor visual

I'm trying to run an old (~1995) Windows game under Wine, but it requires 256 colours and won't work any higher. I've checked out the 256 colour hacks page and the X methods don't work, because I use the FGLRX drivers and they don't support 8bpp, so I'm trying VNC. I've installed vnc-server and vnc so I can play it through a 256 colour VNC connection, but so far I can

Hi. This post follows on from: http://lists.xensource.com/archives/html/xen-devel/2005-04/msg00185.html And is possibly related to the bug referenced here: http://bugs.sun.com/bugdatabase/view_bug.do;:YfiG?bug_id=4335360 In summary: Java processes are doing odd things. 1) It appears that number values are mysteriously changing. e.g. if you look at the Hashtable error there is no way the

On 21/06/17 04:38 PM, Daniel Vetter wrote: > On Tue, Jun 20, 2017 at 09:25:25PM +0200, Peter Rosin wrote: >> This makes the redundant fb helpers .load_lut, .gamma_set and .gamma_get >> totally obsolete. >> >> I think the gamma_store can end up invalid on error. But the way I read >> it, that can happen in drm_mode_gamma_set_ioctl as well, so why should >>

Hello, I have an example of a 2 paneled plot, with two different aspect ratios displayed on one page. An example would help n=20 x1 <- cumsum(runif(n)) x2 <- cumsum(runif(n)) d <- data.frame(val=c(x1,x2),id=c(1:n,1:n), nt=c(rep("A",n),rep("B",n))) u1 <- xyplot(val~id | nt, data=d,aspect=1,layout=c(1,2)) u2 <- xyplot(val~id|nt, data=d,aspect=0.5,layout=c(1,2))

Hi We are about to publish a book, which contains figures made with R plots. An important detail that we did not take into account is that the book will not be printed in 4 colors (cmyk mode), but only 2 (black +"spotcolor"). The spotcolor we use is part of the big Pantone family. The problem is that both pdf() and postscript() offer either rgb or cmyk, but no spotcolors such as

hi! I would like to produce simple black and white postscript figures for publishing. A black/white or grayscale or CMYK colormodel can be used, but not RGB colours. Can I produce postscript graphs in R that satisfy this? Following an earlier advice on the help-list I have tried using Photoshop to convert - but this seems to convert the vector format into raster format - giving larger,

I've writen this function (imagenrgb) to display a (m,n,3) array as a RGB image with ngris^3 colors and,optionally, stretching. If option ver=F, it does not display but saves a pseudocolor version of the image as a list (so that subsequent displays are faster). I'd appreciate feedback and improvements and hope that it's useful for others. Example of use: > dim(imatest) [1] 100

On Sat, 16 Mar 2002 ripley@stats.ox.ac.uk wrote: > On Sat, 16 Mar 2002 Edwin@balpol.tudelft.nl wrote: > > > > The system in question (like many UNIX workstations) has both Pseudo and > > truecolor visual types available, however the default type points to an 8 plane > > PseudoColor visual. > > I believe that is unusual. Sun Xservers allow you to set the default

I've put up R-0.64.0.tgz up for FTP from Auckland a little while ago. As usual, don't get it from there unless you are desperate, but wait for it to be mirrored at a CRAN site near you within a day or two. For those who *are* desperate, I've left a copy in ftp://blueberry.kubism.ku.dk/pub/R-devel/R-0.64.0.tgz (Be gentle, that's my desktop PC!) There's also a version split

I've put up R-0.64.0.tgz up for FTP from Auckland a little while ago. As usual, don't get it from there unless you are desperate, but wait for it to be mirrored at a CRAN site near you within a day or two. For those who *are* desperate, I've left a copy in ftp://blueberry.kubism.ku.dk/pub/R-devel/R-0.64.0.tgz (Be gentle, that's my desktop PC!) There's also a version split

Hi. GENERAL: Is there a general method for inferring default device settings, particularly 'width' and 'height', that works for all devices? AFAIK, the answer is no, but there might be functions out there that I don't know of. POSTSCRIPT SPECIFIC: If not, I'm considering implementing such a method myself. Is it possible for R to infer the default 'width' and

Dear R users, I have a lot of experience with traditional R graphics, but I decided to turn to trellis as it was recommended for spatial graphs by the sp package. In traditional R graphics I always first set the size of the device region absolute units (e.g. mm) and then I firmly fix the inner margins with mai and the outer margins with oma also in absolute units. What is left from the device

My goal is to create a graph with one column and three rows into a single graphic. The mfrow, mfcol, and layout functions all have the same effect: three graphs are produced in a single pdf file, having one graph per page. This is not what I want (I didn't want multiple pages). Just before I sent this post, I was able to generate the desired output with split.screen. Is this the expected

Hi all, these are the remaining unapplied patches of the ARM HDLCD patch series. Changes in v7: - rebased on b61ed421d2c85b5b106c63f2c14f8aa162b282f0; - turn more printk and panic into early_printk and early_panic. Changes in v6: - rebased on 77d3a1db3196b1b5864469f8d3f41d496800c795; - remove useless initializations to NULL in lfb_init; - more compact checks in lfb_init. Changes in v5: - move

I've fixed the original report and Tom's first. Someone had incorrrectly arranged for most of the initialization to be done only once per session. I did ask before 1.3.0 what the intention was .... For pseudocolor devices at least this was biting since the palette was not re-initialized. I don't see point two on my system, and Martin's point about interruption was first shown

Hi Peter Yes, that looks roughly right to me. I would be in favour of your option (b), partly because it is probably easiest and partly because that retains the basic graphics device startup logic pattern that is replicated across all(?) graphics devices. Paul On 28/04/19 11:39 AM, peter dalgaard wrote: > I had a look at the current code, and AFAICT it has essentially the same structure