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

Windows 10: each "virtual desktop" uses the same MaxTo layout #543

Closed
dramamask opened this issue Mar 9, 2020 · 9 comments
Closed

Windows 10: each "virtual desktop" uses the same MaxTo layout #543

dramamask opened this issue Mar 9, 2020 · 9 comments
Assignees
Labels
bug Confirmed bug in MaxTo.
Milestone

Comments

@dramamask
Copy link

MaxTo 2.01
Windows 10.0.18363

Previously, MaxTo would remember a layout for each "virtual desktop". If you loaded a layout it would only effect that particular "virtual desktop"... which was great because I use different layouts for each of my four desktops.

Since about two weeks ago the same layout is used on each of the "virtual desktops". When I load a MaxTo layout on any of my desktops, it now applies to all desktops.

I don't see any errors in the logs.

@vegardlarsen
Copy link
Member

@dramamask Have you enabled it in the settings (bottom of screenshot)?

image

@vegardlarsen
Copy link
Member

Closing this due to no feedback. Will re-open if requested.

@dramamask
Copy link
Author

Sorry for the late reply. Yes, that is enabled:

image

This used to work for me, until the latest Windows 10 update.

@vegardlarsen
Copy link
Member

OK, then it could be a problem with an underlying change in the Windows 10 APIs. We use some undocumented APIs to enable this support, and Microsoft has been known to change it before.

@vegardlarsen vegardlarsen reopened this Mar 20, 2020
@vegardlarsen vegardlarsen self-assigned this Mar 20, 2020
@vegardlarsen vegardlarsen added the bug Confirmed bug in MaxTo. label Mar 20, 2020
@vegardlarsen
Copy link
Member

I can reproduce this locally, and I am looking at it.

@vegardlarsen vegardlarsen added this to the 2.1.0-alpha.4 milestone Mar 22, 2020
@vegardlarsen
Copy link
Member

Thank you for this report, @dramamask. This boils down to a bug in a library we are using. Specifically this bug.

I have successfully managed to fix the issue locally; but since we need to fork that project and set up our own builds of it; I do not have a test build ready for you at this time.

If you are interested in a preview build of this fix, please e-mail support AT maxto DOT net with a reference to this issue, and I'll send it over as soon as I have it ready. PS! Due to the corona lockdown I will not be working for the coming 4 days; so this may take a while.

@dramamask
Copy link
Author

Thank you for jumping on this! Much appreciated.

@vegardlarsen
Copy link
Member

This issue has been solved, and will be in 2.1.0-alpha.4.

@shie-erlich
Copy link

this is happening to me on 2.1.1.
is there a workaround?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Confirmed bug in MaxTo.
Projects
None yet
Development

No branches or pull requests

3 participants