-
Notifications
You must be signed in to change notification settings - Fork 37
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
add customizable responses's time for prompts #291
Comments
Can you please give an example? AFAIK RStudio shouldn't be timing out in any of the prompts exposed to |
The mentioned code is in the remote.R line 65
|
Ahh, thanks -- so this is specifically for the case where |
Well, I called it from a R Job, Besides, I filled the prompt manually. |
jonovik
added a commit
to jonovik/rstudioapi
that referenced
this issue
Jul 4, 2024
…tudio#291. Revised function signatures: showDialog(title, message, url = "", timeout = 10) callFun(fname, ...) callRemote(call, frame, timeout = 10) Original function signatures: showDialog(title, message, url = "") callFun(fname, ...) callRemote(call, frame) To avoid adding arguments to callFun(), I make an object of list(...) and check whether it has a `timeout` element, then callRemote() with two or three arguments as needed.
jonovik
added a commit
to jonovik/rstudioapi
that referenced
this issue
Jul 4, 2024
…tudio#291. I've added a `timeout` argument to showDialog() and callRemote() as described below, and added logical to callFun() to propagate a named `timeout` argument to callRemote() if running as a job. Revised function signatures: showDialog(title, message, url = "", timeout = 10) callFun(fname, ...) callRemote(call, frame, timeout = 10) Original function signatures: showDialog(title, message, url = "") callFun(fname, ...) callRemote(call, frame) To avoid adding arguments to callFun(), I make an object of list(...) and check whether it has a `timeout` element, then callRemote() with two or three arguments as needed.
jonovik
added a commit
to jonovik/rstudioapi
that referenced
this issue
Jul 4, 2024
…tudio#291. I've added a `timeout` argument to showDialog() and callRemote() as described below, and added logic to callFun() to propagate a named `timeout` argument to callRemote() if running as a job. Revised function signatures: showDialog(title, message, url = "", timeout = 10) callFun(fname, ...) callRemote(call, frame, timeout = 10) Original function signatures: showDialog(title, message, url = "") callFun(fname, ...) callRemote(call, frame) To avoid adding arguments to callFun(), I make an object of list(...) and check whether it has a `timeout` element, then callRemote() with two or three arguments as needed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be possible add customizable response's time for possible Rstudio form's prompts?
I am looking at the code and this time was set in 10 secs, which is too short to fill them.
I have been having problems running jobs from RStudio if it has Rstudio prompts inside.
The text was updated successfully, but these errors were encountered: