Dear R-Devel list members
I'm facing as problem already known and linked to the use of
getGraphicsEvent(prompt = "Waiting for input",
onMouseDown = NULL, onMouseMove = NULL,
onMouseUp = NULL, onKeybd = NULL,
onIdle = NULL,
con
On Thu, Feb 19, 2009 at 9:27 AM, Sklyar, Oleg (London) <
oskl...@maninvestments.com> wrote:
> Dear Simon,
>
> thanks for comments.
>
> I better give a bit of a background first. We are analysing time series of
> financial data, often multivariate and with say 200K samples. It is quite a
> frequent
Hi Simon,
Yes I agree with you on the definition of IG (selection, data query,
...), but I only meant to respond to Oleg's "R lacks functionality
that would allow displaying of interactive plots with two distinct
functionalities: zooming and panning." I thought that was just a
problem to adjust th
On Feb 19, 2009, at 16:36 , hadley wickham wrote:
What we need is a more general framework for interactive graphics -
this
requires more than just a graphics subsystem - you have to depart
from the
concept of graphics objects and include "statistical objects" in
the mix
such that the under
Simon,
as promised I attach a simple package that utilises gtkdatabox. It is
Linux only, sorry for that: as it was hacked together in the last two
hours I did not have time for Windows stuff.
Under my Ubuntu I only had to install libgtkdatabox-dev from standard
repos (which would pull libgtk2-de
> What we need is a more general framework for interactive graphics - this
> requires more than just a graphics subsystem - you have to depart from the
> concept of graphics objects and include "statistical objects" in the mix
> such that the underlying data/statistics etc. can be identified by lin
On Feb 19, 2009, at 11:20 , Yihui Xie wrote:
Well, for the first idea, isn't it easy enough to fulfill zooming or
panning using getGraphicsEvent() in the grDevices package?
Yes, but that's exactly what interactive graphics are NOT about (you
just posted a good "chewing gum" reference from
Dear Simon,
thanks for comments.
I better give a bit of a background first. We are analysing time series of
financial data, often multivariate and with say 200K samples. It is quite a
frequent situation that one needs to display multivariate time series of say
200K rows and 10 columns over th
On Tue, 18 Dec 2007, Byron Ellis wrote:
> I probably missed this discussion, but why not just ASK the device if
> it is interactive? 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
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) wit
I probably missed this discussion, but why not just ASK the device if
it is interactive? 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.
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 Statisti
12 matches
Mail list logo
