Open homerhanumat opened 8 years ago
The problem is that when you are executing within a top-level browser window you can't programmatically close the window (this is a restriction that browsers impose). Shiny does post a "disconnected" message to the containing frame and when a Shiny app is running within an RStudio window this message is caught and the window is automatically closed.
@jcheng5 I think that the browserViewer
should default to running within an RStudio window (I think to do this you just need to run the application just the way a normal runApp call would work). If you don't do this then the "Done" button is effectively broken for all instances of browserViewer
.
Thanks. I'll wait for a change like the one you describe.
On Fri, Jan 22, 2016 at 4:41 PM, JJ Allaire notifications@github.com wrote:
The problem is that when you are executing within a top-level browser window you can't programmatically close the window (this is a restriction that browsers impose). Shiny does post a "disconnected" message to the containing frame and when a Shiny app is running within an RStudio window this message is caught and the window is automatically closed.
@jcheng5 https://github.com/jcheng5 I think that the browserViewer should default to running within an RStudio window (I think to do this you just need to run the application just the way a normal runApp call would work). If you don't do this then the "Done" button is effectively broken for all instances of browserViewer.
— Reply to this email directly or view it on GitHub https://github.com/rstudio/addinexamples/issues/3#issuecomment-174059259 .
@jjallaire I didn't think the captive browser window was directly exposed to us? The default runApp lets RStudio choose I think. I would love to be able to do this.
We set options(shiny.launch.browser) internally so I think if you just allow the default behavior to occur it will go to the captive browser window.
I think you might need a windowViewer function which has this behavior (then browserViewer can continue to force an external browser, perhaps with the proviso that the Done and Cancel buttons won't really work as intended in that case).
On Fri, Jan 22, 2016 at 8:41 PM, Joe Cheng notifications@github.com wrote:
@jjallaire https://github.com/jjallaire I didn't think the captive browser window was directly exposed to us? The default runApp lets RStudio choose I think. I would love to be able to do this.
— Reply to this email directly or view it on GitHub https://github.com/rstudio/addinexamples/issues/3#issuecomment-174106940 .
Suppose an Addin is written to open in a browser window. When the user clicks the Done button, the window darkens but does not disappear. It seems that the window should be made to disappear. However, when I write the app so as to force this action, I see no effect. For example, consider the following modification of the subset Addin:
I can verify that message-handler script makes it into the head of the document, but the message sent in
observeEvent()
appears to be ignored. Am I doing something wrong?