Hello.

I have 3 monitors. Main one in front of me, one to the left and one below the main one. which is a touch display that I don't use 100% of time. I set some apps to open at that specific monitor when it's attached and display fusion IDs it as number "2" ou of 3.

However, the problem begins when I disconnect that touch display and use just the other 2. Displayfusion then ID's the number "2" monitor as the left monitor (not my main display) and apps keep opening and moving towards that instead of remaining on my main display.

What could I do in order to keep dispalyfusion from moving apps to display "2", which is not my main one, when the 3rd dispaly is NOT attached?

Thank you, Keith.

I'll sure test it out! But hey, where exactly is the attached file with the code again?

I can't believe I'm that blind!

On another note, out of curiosity, how come can't I change my displays' ID, not even on windows-side? I even tried to disconnected them all and reconnect them in the order I wanted but it didn't work.

Absolutely flawless, Keith.

Thank you very much for taking the time.

Such a simple solution made a whole lot of difference!

Cheers!

Keith, I`m back seeking some master help again!

I'm assuming this one will be pretty straight-forward for you fellas so I'll shoot:

Sometimes when I disconnect my 3rd display, it will mess up the whole setup and the main primary one will inactivate itself, making so that my 2nd display will be the only one "active" and primary.

I then have to go to displayfusion monitor settings, activate the 1st display back and make it primary again.

Would it be possible to write a script so that every time I disconnect my 3rd display, my two main ones would retain their original settings? Like some sort of constant checking script that make sure they are always set the way I like it, or maybe one that kicks in every time I disconnect the 3rd one?

Hope that's not too tough for you and Thomas!

Normally I don't like to revive old threads, but this was exactly my problem once I started using a Head Mounted Display.

The provided script does solve my problem, but I'm wondering in Triggers why we can't identify the monitor by its own unique identity?

When I look at the Monitor Configuration screen, you clearly can identify each monitor by name. Which means you can probably read all sorts of identifying data from the monitors that provide it.

What I'm suggesting is to provide an option to let us select the monitor by its current number, but have the trigger use the detailed data available to correctly identify the monitor even if the number changes.

I realize that doesn't work for all (probably older) displays, but there would always be a fallback to the current monitor number approach.