On 12/18/07, Byron Ellis <[EMAIL PROTECTED]> wrote:
> I probably missed this discussion, but why not just ASK the device if
> it is interactive?
That's done if the device is open. deviceIsInteractive() takes away
the guessing even when it's not (the use-case is when you type
example(something) without a device open, and R has to decide whether
to set par(ask = TRUE) just by looking at getOption("device")).
> I can easily imagine a case where a device might be
> interactive or not depending on how it was started. In fact, I don't
> have to imagine a case since the Quartz device in R-devel can have
> exactly this behavior. Something like a Cairo device might also have
> this behavior, though I don't know if the current Cairo devices
> support it.
If there's ambiguity, you can choose not to use deviceIsInteractive.
You'll still be OK once the device is open (I don't think there's much
more that can be done).
-Deepayan
> On Dec 18, 2007 4:34 PM, Paul Murrell <[EMAIL PROTECTED]> wrote:
> > Hi
> >
> > For all developers of add-on graphics devices: please note the
> > existence of deviceIsInteractive() for adding your device to the list of
> > devices for which dev.interactive() returns TRUE. (Available since R
> > 2.6.0; thanks to Brian Ripley I think)
> >
> > Paul
> > --
> > Dr Paul Murrell
> > Department of Statistics
> > The University of Auckland
> > Private Bag 92019
> > Auckland
> > New Zealand
> > 64 9 3737599 x85392
> > [EMAIL PROTECTED]
> > http://www.stat.auckland.ac.nz/~paul/
> >
> > ______________________________________________
> > R-devel@r-project.org mailing list
> > https://stat.ethz.ch/mailman/listinfo/r-devel
> >
>
>
>
> --
> Byron Ellis ([EMAIL PROTECTED])
> "Oook" -- The Librarian
>
> ______________________________________________
> R-devel@r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel
>
______________________________________________
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
