Hi.
On Wed, Dec 21, 2011 at 4:20 AM, beetonn wrote:
> Thanks, Henrik! That's given me some food for thought, and evalWithTimeout
> certainly seems to be a nicer way of doing this than setTimeLimit.
>
> I should probably explain a little more clearly: I want to stop
> getGraphicsEvent() without
Thanks, Henrik! That's given me some food for thought, and evalWithTimeout
certainly seems to be a nicer way of doing this than setTimeLimit.
I should probably explain a little more clearly: I want to stop
getGraphicsEvent() without stopping the program flow (assume we're running the
code fro
...because you're catching the timeout error with try() so it has not
effect, and hence the while(TRUE) {} loop keeps running.
Without knowing anything about graphics event handlers per se, here's
an alternative to catch the timeout event:
library("R.utils");
plot(0, 0);
eventEnv <- getGraphicsE
Dear R-helpers,
I've just started playing with getGraphicsEvent() in R, and was wondering if
there is a simple way to stop this function waiting for input after a
pre-defined time, instead of relying either on a non-NULL value from one of the
event handlers or for a user-interrupt for it to ha
4 matches
Mail list logo