Selected region setting is not loaded on windows start

[daniel-rabe]

Change Region -> select preset -> Use region

reboot

no preset selected

System: Windows 10
Monitor: philips 439p9h

MaxTo Version 2.2

[github-actions]

Thank you for creating your first issue. We will get to it as soon as possible. This is an automated message designed to manage your expectations. We will most likely respond to your message during Norwegian business hours. If you should think of any additional information, please feel free to add it as a comment. If you are reporting a bug or incompatibility, make sure you include the versions of MaxTo, Windows and any incompatible program.

[daniel-rabe]

the issue is caused by the "Virtual desktops" setting @ Monitor

"Virtual desktops"-Option unchecked works like before update, the last preset is loaded on windows start

when the option is checked no preset is loaded on windows start (i changed region after checkbox toggle)

[lindsaytalbot]

the issue is caused by the "Virtual desktops" setting @ Monitor

"Virtual desktops"-Option unchecked works like before update, the last preset is loaded on windows start

when the option is checked no preset is loaded on windows start (i changed region after checkbox toggle)

Thanks for following up. Had the same issue and unticking the option under Monitor > Virtual Desktops also fixed it for me.
This button is ticked by default so I suspect a lot of users will have this problem

[fweb]

the issue is caused by the "Virtual desktops" setting @ Monitor

"Virtual desktops"-Option unchecked works like before update, the last preset is loaded on windows start

when the option is checked no preset is loaded on windows start (i changed region after checkbox toggle)

Fixed for me as well. Maxto 2.2.0

[vegardlarsen]

I can confirm that this bug is related to the virtual desktops feature. Unfortunately my testing didn't uncover it, as it only happens after a reboot. It appears to be caused by the fact that virtual desktops gets a new GUID after a reboot, which means MaxTo no longer knows which virtual desktop this is for. This is going to be tricky to fix; if we replace the GUID by a index instead, this means that if you have 3 virtual desktops, and delete the middle one, the regions that used to be on the virtual desktop you deleted would now apply to the last virtual desktop (the previous nr 3).

[techbech]

the issue is caused by the "Virtual desktops" setting @ Monitor

"Virtual desktops"-Option unchecked works like before update, the last preset is loaded on windows start

when the option is checked no preset is loaded on windows start (i changed region after checkbox toggle)

Thank you, this was what I was looking for. The change was driving me mad

[RhinoFox]

... This is going to be tricky to fix; if we replace the GUID by a index instead, this means that if you have 3 virtual desktops, and delete the middle one, the regions that used to be on the virtual desktop you deleted would now apply to the last virtual desktop (the previous nr 3).

I prefer a index above nothing. I've 3 virt.desktops and have it all the time. Sometimes I've four of them and delete the fourth as it is my temp-one. I presume not many people delete virt.desktop in between.

What was the difference with version 2.1.x That was working fine.

Pos.Solution: Can't you store the GUID and indexes in a table and replace the GUID's with the new ones after a restart?

[KimmoJ]

It does not in fact work fine on 2.1.5, it also has this issue; I've been on 2.1.5 since 2.2 started acting weird with windows and minimizing stuff. Just FYI. For me the virtual desktop unchecking is a viable workaround, though, going to have to try that.

[nrz0]

@vegardlarsen

Unchecking Virtual Desktops did NOT resolve for me in 2.2.0. Still losing custom regions on reboot.

[nrz0]

Update: I changed the Monitor identifier from "Properties" back to "Serial number (default)" and now it's working properly with "Virtual desktops" unchecked. I only changed it to Properties to try and fix this bug, so it has resolved the issue for my purposes (I don't use virtual desktops).

[vegardlarsen]

I have found and implemented a possible solution to this issue. To help me test, please e-mail support@maxto.net with a reference to this issue, and I will send you a private build where it should be fixed.

Unfortunately, the fix to this requires us to store some additional information with your monitor configuration, so this won't magically work after updating to a new release. First, we need to start writing some extra information to each monitor configuration file, which then lets the file become a searchable candidate in the cases where MaxTo cannot find the regions for a monitor. Usually, this should just be a manner of opening up the change regions screen and pressing "Use regions" on each virtual desktop.

[vegardlarsen]

I have released version 2.2.1-alpha.1, which contains the fix to this issue. Set your Release channel to "Alpha" in MaxTo's settings, under Updates, to get it as soon as possible. Please report back on whether this solves the issue for you. If it does, I will release the changes as version 2.2.1 for everyone.

[Michael5122]

Hello everyone,
I found it difficult to deactivate the virtual desktops to solve this issue.
In my desktop (windows 10 desktop with Philips 499P monitor) I only have the "multitasking - work with multiple windows" settings page,
the only options are "Snap Windows" and "Timeline"

Can you help us identify what to deactivate? Thanks!!

[vegardlarsen]

@Michael5122 You need to deactivate this in MaxTo's settings, not your desktop settings. Hit Ctrl+Windows+T to open them, and the window looks like this (sorry about the language setting here, its the bottom setting on the screen):

I am closing this as nobody has reported any issues with this fix.