Window size/position on a per-monitor basis

WARNING: You currently have Javascript disabled!
This website will not function correctly without Javascript enabled.

buster2006

6 discussion posts

New user here, bought a while back (thanks Steam sale!) but only just getting around to setting up.

I've had a quick look around but havn't been able to find a solution to my problem. I'm wondering whether it's possible to set something up to do the following;
x2 monitors, Chrome shortcut on each monitor's taskbar. If I click the shortcut on monitor #1, Chrome opens to a specific size and location on monitor #1. Clicking the shortcut on monitor #2 opens Chrome maximized on monitor #2.

I've had a quick look at triggers, but I can't seem to get it to work.

Any help greatly appreciated. DF seems like a very handy app, but all the options are a little overwhelming for a new user.

Feb 9, 2020 (modified Feb 9, 2020) • #1

You can do this with Triggers, but web browsers are a bit tricky. You'll need to add part of the page title that the shortcut opens to (e.g. "Gmail") in the Window Text field, and also set the delay for checking the match conditions, because the page needs to be loaded before DisplayFusion checks the window text condition.

I've attached a sample screenshot.

Hope that helps!

• Attachment: ChromeTrigger.png [42,325 bytes]

ChromeTrigger.png

Feb 11, 2020 • #2

buster2006

6 discussion posts

Thanks Keith, that appears to work.

For anyone else wanting to do this; 2nd monitor shortcut has the "--start-maximized" command line argument, 1st monitor shortcut uses the above settings.

The start-maximized option is specific to Chrome, I'm wondering if there's a way of making any "app" do this (e.g., explorer)? Same setup; main monitor shortcut opens at specific size/location, 2nd monitor shortcut opens maximized.

Feb 14, 2020 • #3

You could add a scripted function (Settings > Functions tab) like this:

Code
Copy
Select All

using System;
using System.Drawing;

public static class DisplayFusionFunction
{
    public static void Run(IntPtr windowHandle)
    {
        if (BFS.Monitor.GetMonitorIDByWindow(windowHandle) == 2)
        {
            BFS.Window.Maximize(windowHandle);
        }
    }
}

That will maximize the winodw if it's on monitor 2. You can then run that from your Trigger rule

Hope that helps!

Feb 14, 2020 • #4

buster2006

6 discussion posts

Thanks for taking the time to help out Keith, appreciated.

I can't seem to get this one working though. Do I just need one trigger rule for explorer.exe with multiple actions (one for size position on monitor 1 and another for maximize on monitor 2), or am I doing it completely wrong?

Feb 15, 2020 • #5

Yeah, having both would work, with the one that runs the scripted function positioned after the other one in the list on the Triggers tab. Make sure that the "Stop processing" option is disabled for both.

Feb 19, 2020 • #6

buster2006

6 discussion posts

Hmm, I must be doing something wrong here. Apologies for my lack of understanding and thanks again for the great customer support

Triggers are set up as per the attached images.
Opening explorer on monitor 1 is fine; it moves/resizes to the correct position. Opening explorer on montor 2 however doesn't maximize, just moves it over. If I close this window, then re-open on monitor 1 it maximzes briefly on monitor 2, then moves over to monitor 1 and resizes accordingly.

Running DF taskbar on monitor 2 with the "Force app to start on same monitor..." option enabled for the shortcut.
Script is copied/pasted from above, but monitor number changed to "1" (I have my monitors set up the other way around; "2" is my primary, "1" is the secondary (had to do this as I don't get POST/BIOS output if they're connected to the "correct" ports, but that's a seperate issue, nothing to do with DF)).

[edit] I need to click on monitor 2's desktop first, then click the shortcut, then it works..? Any way of doing it without the additional click?
[edit2] Nope, clicking the desktop beforehand only maximizes sometimes (<50%). I must be doing something wrong.

• Attachment: Trigger.PNG [52,236 bytes]

Trigger.PNG

• Attachment: Trigger2.PNG [35,080 bytes]

Trigger2.PNG

• Attachment: Trigger3.PNG [30,921 bytes]

Trigger3.PNG

Feb 20, 2020 (modified Feb 21, 2020) • #7

Strange! If you set the "Delay before checking match conditions" option in the maximize trigger to something like 2000, does that make any difference at all?

Feb 21, 2020 • #8

buster2006

6 discussion posts

2000 ms delay doesn't seem to fix it.

Same result as above;
Click shortcut on monitor 1 (primary)
Explorer window opens then moves/resizes to correct position
Close explorer

Click shortcut on monitor 2
Explorer window opens then moves over to monitor 2 at same size (doesn't maximize)
Close explorer

Re-click shortcut on monitor 1
Explorer window opens on monitor 2, briefly maximizes, then moves over to monitor 1 at correct size/position.

So the monitor 1 stuff (size/position) is working totally fine, but there's something amiss with the monitor 2 maximizing functions.

The only other app I have running for dual monitor settings is LittleBigMouse (for mouse cursor DPI alignment) but even with that closed the DF triggers don't seem to work as intended.

Feb 21, 2020 • #9

I think what may be happening here is that the "force shortcut to open on this monitor" option for the shortcut on your second monitor is overriding the Trigger rule. I will check on that though and keep you posted on what I find out.

Thanks!

Feb 24, 2020 • #10

Ok, yep, the taskbar shortcuts will override the Trigger rule. I think what we need here is a "Maximize Window" option on the taskbar shortcuts. In the meantime, I could write up a quick scripted function that would launch both of your File Explorer windows and position them. If you think that will work for you, please let me know

Thanks!

Feb 26, 2020 • #11

buster2006

6 discussion posts

Thanks Keith. It's not super important so I can live without it for the time being. The maximize window feature sounds like a great idea. Looking forward to its implementation. I'll keep my eye on the changelogs.

Feb 26, 2020 • #12

Sounds good, thanks!

Feb 27, 2020 • #13

Was this helpful?

(1)

(-)