Mark Rosten
10 discussion posts
Hi.
I am using a docked and closed laptop into a super widescreen monitor, and using the monitor-configuration to use splits, which works well. So I am using 2 monitor configurations, one for laptop only, and one for docked super widescreen monitor only (both only 1 monitor each).
On un-docking, using the laptop on its own screen, and then re-docking - DisplayFusion does not identify change of monitors and reload the correct monitor config, not putting back the new super wide screen monitor config with splits.
How can I fix this?
I have a workaround as I have allocated a keyboard shortcut combo to the super widescreen monitor, which I have to hit each time docked (a pain) to remember the splits again.
I'm on Windows 10.
Thanks & regards.
Wait, that won't work because it will try to load that profile even when undocking. Your scenario will need a new scripting function that's getting added in the next beta. When it's available, I will give you a sample scripted function that can run via the Trigger.
Mark Rosten
10 discussion posts
Sounds good. Many thanks Keith.
Do you know when this will be available to use?
Kind regards.
Mark Rosten
10 discussion posts
Any news on this?
Thanks & regards
We've released 9.0 Beta 1 so I'm about to look at writing this Scripted Function. When your laptop is docked, is the lid closed? (i.e. do you see 2 monitors in the DisplayFusion Monitor Configuration window, or just one?)
Mark Rosten
10 discussion posts
Normally when docked the laptop is closed, so just the monitor is visible.
Thanks & regards
Ok, thanks! What are the screen resolutions of the laptop display and external display?
Mark Rosten
10 discussion posts
Laptop is 1366 x 768 - though not docked and not visible
Main screen is 2560 x 1080
Thanks
Mark Rosten
10 discussion posts
To clarify, the sequence is this:
1) Laptop closed and docked on uwd monitor
2) Undock and work on laptop open away from office desk
3) Go back to desk, with laptop closed again and re-dock to uwd monitor (only display)
3b) This is when DF does not 'detect' the new config and load my presaved monitor config (with split screen settings)
I just reproduced this now, and went to your Troubleshooting tab - Which errored! With the only line of text saying... Error: Result is invalid.
When used my workaround shortcut key on the monitor config to reapply it manually, and then went into the troubleshooting - it worked - export attached (but not in 'incorrect' state - 3b above).
Thanks.
• Attachment [protected]: DF log - good uwd only.txt [102,143 bytes]
Mark Rosten
10 discussion posts
But won't this run for any profile change, so when undocking and going to laptop only screen - loading the wrong profile?
I can't see how to put criteria into the trigger to address this. It would be useful if you could detect the resolution and use that in the trigger - then I could detect if the screen width was laptop only or larger.
Woops! I missed a step there, sorry! I've edited my steps to add this one in:
"Enable the "Monitor Profile" checkbox in the lower-left of the Trigger window and choose the profile you saved in step 1"
Mark Rosten
10 discussion posts
Hi.
Still no luck.
Have attached 2 troubleshooting logs.
1 for after a redock, when the monitor profile is not detected and not reloaded.
2nd for after a manual reload of monitor profile.
Hope this helps so can fix
• Attachment [protected]: DF log - broken.txt [103,909 bytes]
• Attachment [protected]: DF log - working after manual reload of profile.txt [113,753 bytes]
Ok, when you re-dock but the split profile isn't loaded, if you open the Monitor Configuration window, does it show a profile name in the top-left? It should show the one you created using the steps in post #14.
Mark Rosten
10 discussion posts
No it doesn't. See first screenshot - after dock monitor profile page.
And then I loaded the config, shown in the 2nd screenshot.
Thanks.
• Attachment [protected]: after dock monitor profile page.png [97,199 bytes]
• Attachment [protected]: after monitor profile loaded.png [98,528 bytes]
Ok, can you re-save the Monitor Profile for the docked but no splits setup (the one that happens right after you re-dock), and then make sure that's selected in the Match Conditions in the Trigger rule?
No worries Mark, glad to hear that's all working now!