I have a laptop and two monitors, the latter of which are connected to a docking station.
One of the features I use most is the "Move to Monitor #". My laptop is Monitor 1, the one to its, right is #2, and the rightmost one is #3.
At least, that's what it's supposed to be... I work a lot in the evening with my laptop undocked, but during the day, I dock it to use the other monitors, external keyboard, etc.
The problem is that when I re-dock, sometimes the monitors are in the "correct" order, sometimes they are reversed, so when I do the combos for #2, they are applied for 3#, and vice-versa.
Of course, the "simple" approach is to, when I notice this "bug", to reverse my key combinations, but first I have to notice it (or do tests each time), and then ignore my "muscle memory". Not optimal.
I have another workaround, wherein I modify WindowPadX.ini to reverse the monitors, then shut down and restart WindowPadX... This works sometimes, but for some reasone sometimes it does not.
Oh, and I also modified WindowPadX.ini to include another monitor, namely #3. Here is a sample:
NumpadAdd = WPXA_MoveWindowToMonitor, 2
NumpadMult = WPXA_MoveWindowToMonitor, 3
When the "bug" shows up, I reverse the 2 and 3, shut down the app, and restart (all of which takes a fair amount of time).
Is there some way to do this reversal "on the fly"? I thought perhaps adding a routine to identify - or re-identify the monitors... I've looked through both WindowPadX.ini and WindowPadX.ahk, trying to figure out how to do this, but I guess it's beyond my abilities.
I have a laptop and two monitors, the latter of which are connected to a docking station. One of the features I use most is the "Move to Monitor #". My laptop is Monitor 1, the one to its, right is #2, and the rightmost one is #3. At least, that's what it's supposed to be... I work a lot in the evening with my laptop undocked, but during the day, I dock it to use the other monitors, external keyboard, etc. The problem is that when I re-dock, sometimes the monitors are in the "correct" order, sometimes they are reversed, so when I do the combos for #2, they are applied for 3#, and vice-versa. Of course, the "simple" approach is to, when I notice this "bug", to reverse my key combinations, but first I have to notice it (or do tests each time), and then ignore my "muscle memory". Not optimal. I have another workaround, wherein I modify WindowPadX.ini to reverse the monitors, then shut down and restart WindowPadX... This works sometimes, but for some reasone sometimes it does not. Oh, and I also modified WindowPadX.ini to include another monitor, namely #3. Here is a sample: NumpadAdd = WPXA_MoveWindowToMonitor, 2 NumpadMult = WPXA_MoveWindowToMonitor, 3 When the "bug" shows up, I reverse the 2 and 3, shut down the app, and restart (all of which takes a fair amount of time).
Is there some way to do this reversal "on the fly"? I thought perhaps adding a routine to identify - or re-identify the monitors... I've looked through both WindowPadX.ini and WindowPadX.ahk, trying to figure out how to do this, but I guess it's beyond my abilities.
Thanks!
Salutations, -Paul