Hey there. I'm having a frustrating experience on my second monitor where the start menu and taskbar will flash, then lose focus behind another window. So far I've reproduced this hiding issue behind Chrome, Firefox, Teamspeak, Discord, Audacity, and Windows Explorer.
I'm on Windows 10, latest build. Have Classic Shell installed for some tweaks to the start menu. I've searched both the Classic Shell and DisplayFusion forums for anything similar to this issue, but so far have come up empty-handed.
It looks like it might be moving itself to the bottom of the z-order because a full screen window is detected.
I'm running a game in borderless windowed mode during the attached log. It was the most consistent way to reproduce the issue, which happened multiple times at "2017/04/25 05:21X"
It's nice to be able to use my second monitor's start menu between matches to find music, documents, etc. I'm not running in true fullscreen mode, though that seems to cause the same issue even if I'm tabbed out of the game.
If you need anything else from me, lemme know. Thanks!
In the Settings > Advanced Settings window, can you try enabling the "Ignore Full Screen Windows" option to see if that helps?
Did that, still having the same issue.
I also was able to reproduce this without having a borderless windowed game running. This should be in the included log file, it happened multiple times at "05:44X"
Did you have the Start menu open at the time? The log is saying it's forcing the taskbar to the bottom because it's detecting the Classic Start Menu as being open.
Yes I had the start menu open when that occurred, though it gets hidden behind and I cannot interact with it. I have Classic Shell installed, so when I click on the start button on either monitor it opens the Classic Shell start menu and not the Windows 10 native start menu. Is that what you meant by "classic start menu?"
It's also not just the taskbar that disappears. The entire start menu pane gets hidden behind any open window.
Just a quick update, I haven't forgotten about this. I had another look at the log today and noticed something else of interest that I need to check in with our devs on. I'll post more news when I have some
We've just released a new DisplayFusion beta version (http://www.displayfusion.com/Download/Beta/) and this issue should be all fixed up. Please let us know if you run into any trouble after updating.