I could reproduce the issue several times and came up with different results depending how fast or slow the cable was plugged in again. Maybe it's important to notice that I'm unplugging the cable directly on my graphics card, not the cable that is plugged in right to the monitor.
So I unplugged the cable for about 30secs and everything was fine,
except that the taskbar shortcuts were gone after the monitor was unplugged but luckily they're back again after I plugged the cable in.
The other result was like mentioned in my initial post when I'm unplugging the cable for just about a second or less: The shortcuts disappeared and were completely gone even when I was plugging in the cable again. DisplayFusion takes a while to "recognize" the new situation and finally starts rendering the taskbar.
As already mentioned my monitor setup is like this:
Monitor #1 - left, the display that gets unplugged.
Monitor #2 - center, primary display.
Monitor #3 - right, the display with the issues.
When the left monitor ( #1 ) is unplugged the monitor layout becomes something like this ( which makes a lot of sense IMO
):
Monitor #0, former #1 - left, not plugged in <-- not showing up, why shouldn't it ?
Monitor #1 - center, still primary monitor
Monitor #2 - right, the missing-shortcuts display
I guess the source of this problem can be tracked down to a method that could potentially be responsible for rendering the taskbars and shortcuts which may be lagging behind as the re-plugging was too fast. This causes something like that DisplayFusion assumes that my right monitor, which has temporary ID #2 (
the same as my primary monitor has when all 3 displays are connected! ),
is my primary monitor, so DisplayFusion doesn't render the shortcuts but it still renders the taskbar, which may have an additional "if", a faster response-/update-time ( oh yea, we do like asynchronous programming! ) or some other kind of mechanism to prevent weird situations like this.
Maybe my few brainfarts (
) and my testing can help you guys hunting down the issue more easily
Greetings!
[EDiT]
Oh and yea, restarting DisplayFusion fixes the issue every time it occurs
Lastly tested 5 seconds ago as the problem was still presented
[EDiT2]
In Beta 6 I can still reproduce the bug.