-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
interactive() is problematic for "my" typical usecase #11
Comments
so you mean an additional parameter? I usually run |
That doesn't really work for me since my drivers are themselves functions, I guess I could write further R scripts which call the drivers, rather than calling them "interactively". I guess that would even be a good way to keep track of the exact parameters used for a given analysis. Lemme think about it and I'l get back to you.
I guess so, but more usefully it could also be done through the options() framework, with the default as
or something like that. The |
I would really like to re-iterate this point. I don't think that a plot routine should open new devices... |
I don't see, why not. There is no other way to have multiple X11 plots opened by a single plot function. However, I see your point. So, what about something like the following additional condtions to
to only open a new window if there is no other driver used than X11? |
See commit 82aed14 ... |
in urbach/hadron master branch |
this is fixed now, isn't it? |
Yes, I think so, I'll close the issue. |
They way I use R makes the usage of
interactive()
a bit problematic. My analysis drivers have loads of parameters in order to be suitable for different analyses (as far as that is possible) and as a result I generally run them from an interactive session. It would be helpful for me if interactivity as a reason for callingX11()
to get new windows could be an internal state rather than what is reported byinteractive()
. What do you think?The text was updated successfully, but these errors were encountered: