Quote:
I am running a registered trial version of DisplayFusion. I have a Windows 10 PC with eight different monitors connected to it. They're all showing up correctly in layout by number and position in Windows and in DisplayFusion.
I have a Powershell script (executed with a desktop shortcut) that opens multiple Microsoft Edge browser windows. This script functions successfully. The windows open - each in its own Microsoft Edge browser window.
Example of portion of script that opens Edge windows:
Start-Process -FilePath msedge -ArgumentList '--new-window www.google.com'
Start-Process -FilePath msedge -ArgumentList '--new-window www.bing.com'
Here's my problem: I want each window, identified by the WINDOW TITLE (usually html 4 title tag) of the browser page, to go to a specific monitor, in maximized mode, by monitor NUMBER. No relative positioning. No spanning. No split screen stuff. Simply by monitor number and the window name.
DisplayFusion seems to support these types of actions. I have triggers set up based on executable (Edge) and the title of the HTML page (as shown in the tab). Note, there are NOT multiple tabs per window - only one in each.
For the life of me I can't seem to get it to work. I run the powershell script. The windows open. However, they do not maximize and they do not appear on their assigned monitors as defined by DisplayFusion triggers. I've spent hours on this so far, trying variations of the window titles (the title of the html page as shown in the browser tab), using (and not using) the Edge executable as defined by the options in DisplayFusion GUI. They USUALLY open on an a single individual monitor. If I close a window and open it up on a different monitor (by hand), it MAY or may not show up on that same monitor when I run the script again, but DisplayFusion doesn't seem to be involved at all in that decision, it seems to be a Windows random thing. I have tried using the little target drags in DisplayFusion to identifiy particular windows. I have even tried clearing out all cache, permission and history in Edge before running the Powershell script. This made no positive difference in behavior.
Help!!