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?
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?
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:
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.
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?
