App positions moving to primary monitor when Windows locks. It worked on another machine

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

Tony89

56 discussion posts

I had a Windows 7 machine which had some triggers setup to preserve the icons and window position. It worked fine for years. I got a new Windows 10 machine and I restored the DisplayFusion settings from the Windows 7 machine. The Windows 10 machine sleeps at 20 minutes. When I unlock the machine, I noticed all the apps from secodary monitor moved to the primary one.

I have a 'Save Windows Positions' trigger set to System Idle event at 54 Idle Timeout. I have a 'Move to 2nd window' trigger set ato 'Monitor Profile Changed' event. I can't remember what this triggers does. Move what to 2nd window? What is 2nd window? 2nd monitor? It's not clear.

Anyway, I am not sure why the same settings are not working on the new machine. It's teh same monitors and cables. Just the laptop and OS were changed and I restored the settings. Windows sleep is set to 20 minutes. The 54 seconds for the save trigger should happen multiple times before the sleep kicks in. Using default profile.

I also have two trigger on function 'Load Desktop Icon Profile' I assume these are to restore the desktop icons.

It seems I am missing something but not sure what. What's the trigger or thing that loads the window positions that were saved in the save trigger?

Oct 31, 2019 • #1

Tony89

56 discussion posts

I am going to restore the settings from a Windows 10 machine and test. Then I will follow up here.

Nov 1, 2019 • #2

Tony89

56 discussion posts

The other machine has the same settings. I am using displayport. I want to knwo what to do so that the apps are restored to their original monitors.

Nov 1, 2019 • #3

Could you send me a copy of the Settings backup so that I can have a look at the Trigger rules you have setup?

Nov 4, 2019 • #4

Tony89

56 discussion posts

Quote:

Could you send me a copy of the Settings backup so that I can have a look at the Trigger rules you have setup?

Send it to where?

Nov 5, 2019 • #5

You can attach it in a reply here

You can export them with the Export Settings button on the DisplayFusion Settings > Options tab.

Thanks!

Nov 5, 2019 • #6

Tony89

56 discussion posts

Quote:

You can attach it in a reply here

You can export them with the Export Settings button on the DisplayFusion Settings > Options tab.

Thanks!

The settings has the license key and my email address. Are you saying only you can download the attachment?

Nov 5, 2019 • #7

Yep! When you attach the file, there's a "Protect these attachments" checkbox. If that's enabled, only Binary Fortress staff can download them.

Thanks!

Nov 7, 2019 • #8

Tony89

56 discussion posts

Quote:

You can attach it in a reply here

You can export them with the Export Settings button on the DisplayFusion Settings > Options tab.

Thanks!

The settings has the license key and my email address. Are you saying only you can download the attachment?

• Attachment [protected]: DisplayFusion Backup (2019-10-31 @ 20-23, 9.5.0.0, TONYPC).reg [247,194 bytes]

Nov 12, 2019 • #9

Thanks! Could you try changing the "Monitor Profile Changed" Trigger to run "Run Function: Restore Window Positions from Last Save"?

Nov 13, 2019 • #10

Tony89

56 discussion posts

Quote:

Thanks! Could you try changing the "Monitor Profile Changed" Trigger to run "Run Function: Restore Window Positions from Last Save"?

The apps are still moving to the primary monitor.

• Attachment [protected]: DisplayFusion Backup (2019-11-21 @ 15-56, 9.5.0.0, CA003-LT107305).reg [247,162 bytes]

Nov 21, 2019 • #11

Ok, could you try this and let me know what happens?

Disable the Trigger rules
On the Settings > Functions tab, set key combinations on the "Save Window Positions" and "Restore Window Positions from Last Save" functions
Save the positions via the key combination before leaving the computer
Restore the positions via the key combination after unlocking it

If this works, we just need to figure out what's wrong with the Trigger rules

Nov 22, 2019 • #12

Tony89

56 discussion posts

The keys work.

What is the trigger for when the the monitors go back on? This is not when desktop is unlocked or Windows comes out from sleep mode.

Dec 2, 2019 • #13

There isn't a Trigger for when the monitors come back on, but the Monitor Profile Changed trigger should work because it will detect the Monitor Profile when the monitors are on. So two questions:

When you power the monitors on, if you open the Monitor Configuration window, does it show "Profile Detected: " in the top-left?
If so, is that profile selected in the Match Conditions for the Monitor Profile Changed trigger rule?

Dec 3, 2019 • #14

Tony89

56 discussion posts

I don't see it. I don't know where it should display. There's no space. Do you have a sample screenshot?

Dec 4, 2019 • #15

Sure thing! It would look like the attached screenshot.

• Attachment: detectedprofile.png [13,938 bytes]

detectedprofile.png

Dec 4, 2019 • #16

Tony89

56 discussion posts

Am I supposed to see this any time I open the monitor configuration? I never see it.

Dec 4, 2019 • #17

Only if you have a monitor profile saved, and it gets detected by DisplayFusion. Could you send me a copy of your troubleshooting info? Here are the steps:

Open the Settings > Troubleshooting tab
Click the "Export Info to File" button
Reply with the file attached

Dec 5, 2019 • #18

Tony89

56 discussion posts

Quote:

Am I supposed to see this any time I open the monitor configuration? I never see it.

• Attachment [protected]: DisplayFusionDebugInfo.zip [29,248 bytes]

Dec 16, 2019 • #19

Thanks! Could you try re-saving the "Default" monitor profile? It looks like something with the monitor configuration (possibly some hidden value in the backend) has changed, so it's not detecting it, which is what's causing the Triggers not to fire.

Dec 18, 2019 • #20

ClaireCJS

44 discussion posts

I feel like this is similar to problems I've had. At what point should DisplayFusion consider this to be one of the bugs that it fixes automatically, rather than having everyoe create a bunch of redundant triggers?

Jul 15, 2023 • #21