X11cairo with antialias="none" buggy under MacOS? - R-devel

Thu, May 1, 2008 4:32 AM #

using

X11(antialias="none")
plot(1:10)

produces an incomplete plot with 2.7.0. under
MacOS 10.4.11: both y-axes are missing.the
y-ticks (except the tick at `2' wich  is missing)
including labels are there.

this happens with  a 1280x854 labtop monitor.

is this known behaviour/a cairo bug?

joerg

Brian Ripley

Thu, May 1, 2008 5:00 AM #

On Thu, 1 May 2008, Joerg van den Hoff wrote:

A feature.  Think about what the help page says about line widths.

Brian D. Ripley,                  ripley at stats.ox.ac.uk
Professor of Applied Statistics,  http://www.stats.ox.ac.uk/~ripley/
University of Oxford,             Tel:  +44 1865 272861 (self)
1 South Parks Road,                     +44 1865 272866 (PA)
Oxford OX1 3TG, UK                Fax:  +44 1865 272595

Joerg van den Hoff

Thu, May 1, 2008 6:07 AM #

On Thu, May 01, 2008 at 01:00:24PM +0100, Prof Brian Ripley wrote:

you are revering to 

*  Line widths in 1/96 inch, minimum one pixel for 'type =
   "Xlib"', 0.01 otherwise.

from the `X11' manpage, right? 

in what respect is line width below 1 pixel a feature for
a screen device? I see that there are new devices `cairo_pdf'
and `cairo_ps' but when using

X11(antialias="none")

I obviously am going to plot to the screen device. where
a line width below one pixel does'nt make sense to me.

what am I missing?

Barry Rowlingson

Thu, May 1, 2008 6:23 AM #

Joerg van den Hoff wrote:

The new "cairo" X11 device with antialiasing off can indeed look awful 
, but if you really don't want antialiasing then try using the good old 
non-cairo X11 device with the 'type' argument:

  > x11(type="Xlib")
  > plot(1:10)


Barry

Joerg van den Hoff

Thu, May 1, 2008 7:46 AM #

On Thu, May 01, 2008 at 02:23:13PM +0100, Barry Rowlingson wrote:

thanks. I found this out while struggling with my original problem 
(cf. other mails in this
thread) and probably will use "Xlib" anyway since cairo seems simply to slow
for interactve use (don't won't to wait repeatedly for some seconds ...).

I actually would argue that at the current state of affairs it would have been
better to have "Xlib" kept as default.

joerg