One more note on stopping at user click. The following is a bit of a
hack but it seems to work. (Note: In the slow function I used "for(i
in 1:500){}" instead of "Sys.sleep(1)" to better simulate a real
slow R-only function):
reallySlowFunction <- function(n=10){
for(i in 1:n){
Thanks for that link to the mac Gtk2, it's been very helpful.
To work around my original problem I've decided to just have the gui
be a seperate function that returns the parameter values entered. Then
I'll call that function from within a non-gui function -- so have the
window close and the
On Feb 12, 2008 1:51 PM, Peter McMahan <[EMAIL PROTECTED]> wrote:
> Thanks, that's very helpful. Unfortunately Gtk2 is difficult to get
> running on a Mac, so I've been trying the gWidgetstcktk interface.
> It sounds like the behavior you're describing is exactly what I want,
> so it may just be a
Thanks, that's very helpful. Unfortunately Gtk2 is difficult to get
running on a Mac, so I've been trying the gWidgetstcktk interface.
It sounds like the behavior you're describing is exactly what I want,
so it may just be a difference in the TGtk2 and tcltk event loops?
In your example, can yo
Hello,
I'm trying to make a graphical interface for an R function
I've written. A common use for the function is to call it with
specific parameters, and then watch the output as it evolves.
There's not necessarily a logical stopping point, so I usually
use ctrl-C when I'm done to stop it.
I've mad
5 matches
Mail list logo
