-
Notifications
You must be signed in to change notification settings - Fork 151
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
Allow for multiple sessions per user/app combination without queuing events #397
Comments
Hi, the |
Thanks @LEDfan , can I replicate the |
The black navbar is part of the UI of ShinyProxy. As long as you are using ShinyProxy through it's regular web interface this navbar should be available. Only when you are using the |
Okay, that was not clear for me before. Yes, you can open the "Switch Instance" modal from your application code using the following JavaScript code: window.parent.Shiny.ui.showInstanceModal();
window.parent.Shiny.instances.eventHandlers.onShow(null); For example, you can put these lines in the event handler of a button: <button id="switchInstance">Switch Instance</button>
<script>
document.getElementById("switchInstance").addEventListener("click", function(){
window.parent.Shiny.ui.showInstanceModal();
window.parent.Shiny.instances.eventHandlers.onShow(null);
});
</script> I hope this helps! |
Thank you - will have a look at this. I thought that ideally a user will not have to do anytning or click anywhere if i allow them to spin up lets say 2 instances, by just opening a new tab the new instance will be created automatically. |
While using ShinyProxy
2.6.1
and setting up themax-instances
field to 2 in the YAML, I was expecting a user to be able open the app twice (in 2 different tabs or 2 browser instances) and to interact with each tab without having to wait for the other app to finish the task it was running.Instead ,I still have the same behaviour that before (ante version 2.6.0) where if I click on 2 long-running tasks on both tabs, I would still have to wait for the first event to complete until the second get kicked in.
Did I misunderstand the feature here? I could not find the answer in GitHub #395 issue.
Thank you very much @tverbeke , Dylan
The text was updated successfully, but these errors were encountered: