Pinned items on the taskbar remain highlighted after I move the mouse cursor away. It can happen to more than one item at the same time. I have to close DF and run it again to make it go away.

Example GIFs

DisplayFusion v9.6:
https://gfycat.com/grotesqueniceargusfish

DisplayFusion v9.7 beta:
https://gfycat.com/minordesertedblackandtancoonhound

I'm using 9.7 b10 but previous beta versions had the issue as well.

Strange... I presume there's something else I'm missing that triggers this issue.

It happens right away.

FWIW, 9.7 beta 4 doesn't have this issue but beta 5 and onward do. Probably doesn't help, though.

Anyway, this is such a small and obscure issue that I'll just have to live with it. Not worth wasting more time with it, I suppose.

I have a very similar problem (maybe the same?). The circumstances differ slightly. It started happening since at least Beta 6, maybe earlier but I don't remember it happening long time ago, so this is probably a regression. I am using Windows 7 with 'Classic' theming and a vertical taskbar.

It seems to me that this happens more often when the computer is under heavy load (near 100% CPU) and the mouse goes over a taskbar, but I'm not really sure. Some of the pinned items stay highlighted permanently afterwards.

The incorrect highlighting goes away after selecting any option related to the taskbar, like 'Multi-Monitor TaskBar -> Shortcuts -> Combine with Taskbar Buttons', but I have 4 monitors so I have to do it on each of the three additional taskbars separately, which renders this workaround very inconvenient.

I'm attaching two images of the part of the same taskbar, one immediately after (re)starting DisplayFusion and the other done with the problem occuring.

Hope this helps.

Regards,
Michał

Forgot to mention that the difference for me is that it does not happen right away, only after some minutes and sometimes hours and I cannot trigger it 'at will'. I am too busy to notice exactly when this occurs but it always does after some time.

Also, I am attaching my configuration, just in case.

Are you sure that log file from me will help? I'm asking because

• the log file will span several hours, so it can get huge
• I will be unable to 'note the time' as I usually spot the problem long after it occured

Log from the other user might be much more useful, as there it occurs immediately.

Regards

The issue was reproduced from 11:22:19 to 11:22:31 (roughly).

I hope it can help.

So far, so good!

Thanks for the hard work.

Seems the problem disappeared on my side too. Great work on debugging, thanks!