Juli_Juan 2017-12-14 02:45
I have three display profiles for my dual monitor setup hooked up to three macro keys that run the display profile. The three profiles are represented with :) being an enabled monitor and :( being a disabled monitor.
BothMonitors
_______________
| /~~~~~~~~\ ||||
|| ' ' |...|
|| \___/ | |
| \________/ O |
~~~~~~~~~~~~~~~
_______________
| /~~~~~~~~\ ||||
|| ' ' |...|
|| \___/ | |
| \________/ O |
~~~~~~~~~~~~~~~
MainMonitorOnly
_______________
| /~~~~~~~~\ ||||
|| '____' |...|
|| / \ | |
| \________/ O |
~~~~~~~~~~~~~~~
_______________
| /~~~~~~~~\ ||||
|| ' ' |...|
|| \___/ | |
| \________/ O |
~~~~~~~~~~~~~~~
SecondMonitorOnly
_______________
| /~~~~~~~~\ ||||
|| ' ' |...|
|| \___/ | |
| \________/ O |
~~~~~~~~~~~~~~~
_______________
| /~~~~~~~~\ ||||
|| '____' |...|
|| / \ | |
| \________/ O |
~~~~~~~~~~~~~~~
The issue is that if I'm on the profile MainMonitorOnly and run the macro to re-open the MainMonitorOnly profile again then SecondMonitorOnly opens. I don't think it actually opens SecondMonitorOnly but it confuses which monitor is which number because that the other monitor is disabled. The same issue occurs if I open SecondMonitorOnly twice. This is a very insignificant issue but if anyone knows why/how to solve it would be appreciated.
oWo
|
Juli_Juan 2017-12-14 02:46
Oh no, the formatting for the ascii monitors screwed up, but I'm sure you can understand what's going on.
oWo
|
Christian Studer 2017-12-14 04:10
If you're on Windows 7 or later, try the following: with both monitors enabled, run FixMonIds.vbs, this ensures each monitor gets assigned a unique number. You may need to recreate your display profiles after running the script.
Christian Studer - www.realtimesoft.com
|
Juli_Juan 2017-12-14 05:28
Thanks so much, that seemed to fix it :D
oWo
|
