-
-
Notifications
You must be signed in to change notification settings - Fork 565
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
Feature Request: aSPICE multiple instances #583
Comments
Just to mention a couple of additional requests that were discussed - a way
to turn off the extra keys (maybe the menu item can be a toggle rather than
just turning the buttons on), and better contrast for them.
…On Fri, Sep 13, 2024, 11:29 a.m. sim4dim ***@***.***> wrote:
It is critical to have multiple instances of aSPICE running on the same
Mac in order to connect to different hosts at the same time. Perhaps to
have aSPICE launcher window and drag and drop .vv files there to spawn new
windows.
—
Reply to this email directly, view it on GitHub
<#583>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAK3EV7SHB6K5GYHRZUJRN3ZWMAEJAVCNFSM6AAAAABOFTKD5WVHI2DSMVQWIX3LMV43ASLTON2WKOZSGUZDKMJQHE3DINI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Installing the MacOS version of the app, and using a terminal, we can open multiple instances like this at the moment:
|
Ideally, the app should support multiple windows and be able to launch new connections in new windows via something like: https://developer.apple.com/documentation/uikit/uiscenedelegate/supporting_multiple_windows_on_ipad But that would require major surgery to the VNC, SPICE, and RDP backends to ensure they can all run multiple sessions simultaneously without overwriting each other's session data. |
It is critical to have multiple instances of aSPICE running on the same Mac in order to connect to different hosts at the same time. Perhaps to have aSPICE launcher window and drag and drop .vv files there to spawn new windows.
The text was updated successfully, but these errors were encountered: