From deepayan.sarkar at gmail.com  Mon May  7 21:07:17 2007
From: deepayan.sarkar at gmail.com (Deepayan Sarkar)
Date: Mon, 7 May 2007 12:07:17 -0700
Subject: [Rd] Qt device update
In-Reply-To: <Pine.LNX.4.64.0705051521050.15149@gannet.stats.ox.ac.uk>
References: <eb555e660705031752p5a96153fifaabd0d5fdf0bdeb@mail.gmail.com>
	<7B29DCD1-E483-482B-8CCE-526305FE2E9F@r-project.org>
	<Pine.LNX.4.64.0705042200220.29064@gannet.stats.ox.ac.uk>
	<17980.36606.321639.460692@stat.math.ethz.ch>
	<Pine.LNX.4.64.0705051521050.15149@gannet.stats.ox.ac.uk>
Message-ID: <eb555e660705071207m1f05a9c4j316b38b02f7f6aa3@mail.gmail.com>

On 5/5/07, Prof Brian Ripley <ripley at stats.ox.ac.uk> wrote:

[...]

>      o	dev.interactive() regards devices with the displaylist enabled
>  	as interactive, and packages can register the names of their
>  	devices as interactive via deviceIsInteractive().

Thanks. A related issue: 2.5.0's NEWS has:

    o   options(device = ) now accepts a function object as well as
        the name of a function.

(For some reason, I had thought this was true all along, but in any
case) This means that it's now reasonable to do

> options(device = function() x11("", 4, 4))

But then I get (iff there is no device open)

> example(glm)
Error in match(x, table, nomatch = 0) : 'match' requires vector arguments

because dev.interactive() doesn't know about the change yet.
dev.interactive() cannot really do anything useful in this case, but
an error seems too harsh (especially since example(glm) doesn't even
have any graphics).

-Deepayan



[Rd] Qt device update
Deepayan Sarkar