Skip to content
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

Jump to bottom

Fails to launch in the newly created virtual desktop #10467

Closed
cyberduck opened this issue Sep 19, 2018 · 2 comments
Closed

Fails to launch in the newly created virtual desktop #10467

cyberduck opened this issue Sep 19, 2018 · 2 comments
Assignees
@AliveDevil
Labels
core enhancement fixed low priority
Milestone
7.0

Comments

@cyberduck
Copy link
Collaborator

@dkocher created the issue

Application fails to launch in the newly created virtual desktop

Environment: Desktop
OS Build: 17756
OS: Windows 10 Insider Preview, Windows 10
App Version: 6.7.0.0

Repro Steps:

  1. Launch the application.
  2. Application launches successfully.
  3. Now Create the new virtual desktop.
  4. Launch the application.
  5. Observe.

Actual Results:
Application fails to launch in the newly created virtual desktop

Expected Results:
Application should launch in the newly created virtual desktop
Resource
For any questions on app development (or) submission on windows, contact Windows Dev Center. https://developer.microsoft.com/en-us/windows/support
@cyberduck
Copy link
Collaborator Author

@AliveDevil commented

Cyberduck is a single-instance application running in multi-windowed mode.
Opening a Cyberduck instance while having a non-connected browser window open does nothing.
Opening a Cyberduck instance while having a connected browser window opens a browser window in the current virtual desktop just as expected.

There is an API available for moving a window between virtual desktops which could be utilized for the already opened non-connected browser window sitting on another virtual desktop. API for Windows 10 virtual desktops (StackOverflow).

@cyberduck
Copy link
Collaborator Author

@dkocher commented

In a8c9dd3.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@AliveDevil AliveDevil

Labels
core enhancement fixed low priority
Projects
None yet
Milestone
7.0
Development

No branches or pull requests
2 participants
@AliveDevil @cyberduck