Martin

Nope sorry, nothing was changed in this regard

Hey Tommy and everyone else, that is a very interesting find! Taking out the SdcFlags.AllowChanges might, however, break the program for some people. So I have tried to implement the following change: first it will try to switch the settings without SdcFlags.AllowChanges (should preserve refresh rate), if this fails it will try again with SdcFlags.AllowChanges (to make it more compatible to weird setups). I will push the code changes in a second but have also uploaded a beta version over here: https://sourceforge.net/p/monitorswitcher/discussion/requests/thread/c39199d104/...

Hi everyone, in the past months I did some smaller changes and implemented some possible optimizations based on feedback from individual users. Internally I changed some things around in how the Adapter IDs are matched to possibly make the switching more stable on some setups where windows would shuffle the complete internal display setup on each reboot. I did also add a change that could fix problems with restoring the monitor refresh rates. Because both changes are rather fundamental I do not want...

I'm using the predecessor of the G9 myself and have also observed similar issues. However, in my experience it's rather windows that gets completely confused and is really struggling to work with the monitor. When not in PBP I always had huge trouble with window sending the signal to the wrong monitor/cable so that I had to switch inputs in the monitor all the time. Non related to the profile switcher but still very annoying and the reason why I stopped using PBP and just disconnected the second...

Sharing of profiles between computers is not possible, the display paths and adapter settings are quite unique to each individual setup. Often already small changes to an existing setup wil require the creation of new profiles. So sharing profiles between computers won't work 99% of the time, sorry

If I understand you correctly then you also want to switch the input that the monitor is using? Unforunately that's not possible as far as I know, sorry.

I have no idea why this might be happening, all this button does is send a global SC_MONITORPOWER broadcast to the system. This maybe is some energy saving setting in windows. Could it be that the devices which get locked are notebooks with different energy saving settings?

You can do this already by using the Commandline version, see the wiki for details and examples: https://sourceforge.net/p/monitorswitcher/wiki/Home/