Processing Ajax...

Title
Close Dialog

Message

Confirm
Close Dialog

Confirm
Close Dialog

Confirm
Close Dialog

User Image
Astaedus
7 discussion posts
I have monitor (a tv) with a different DPI (text size) setting than the others.
When I click the start button on the (DisplayFusion) taskbar on that monitor, the start menu keeps moving back and forth between my primary monitor and the other monitor in a loop until I click somewhere else to move the focus.

It's probably related to the already reported Windows 10 issue where the start menu briefly opens on the primary monitor before moving to the correct one.
Aug 28, 2015  • #1
Jon Tackabury (BFS)'s profile on WallpaperFusion.com
Can you give this new beta version (Beta 3) a try and let me know if it helps with your issue at all?

http://www.displayfusion.com/Download/Beta/

Thanks!
Sep 1, 2015  • #2
User Image
Astaedus
7 discussion posts
I tried Beta 4 and I no longer have that problem.

But a few new annoyances turned up when I use the start button on the displayfusion taskbars:
- a few seconds after the menu opens, a new task button appears without a title (but with an explorer icon)
- sometimes the start button closes the start menu when it is already closed (doing nothing) or opens it when it is already open (showing the opening animation again)
Sep 3, 2015  • #3
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Glad to hear it! I can't seem to reproduce either of those two issues. For the first one, what is your Taskbar Mode set to on the DF Settings > Taskbar tab?

For the second one, is there a specific set of steps that will cause this to happen?
Sep 9, 2015  • #4
User Image
Astaedus
7 discussion posts
Taskbar mode is set to "All taskbars show relevant windows".

About the second problem: At first I didn't really notice a pattern.
I have noticed that the start button has 3 states: normal, darker and black. I'm not sure, but I think the strange behaviour happens when I click the start button when it is in that "darker" state.

On hover, the background of the start button turns black. On click, the button goes to "darker" and if I keep the mouse cursor on it, it goes to black again after a second or two. If I move the cursor away from the start button before that, the background color goes to "normal" after those 2 seconds.
When I close the start menu, on hover it will turn black, on click "darker" and again after 1 or 2 seconds to black (if the cursor remains on the button)

So.. clicking the start button a second time in those short 1-2 second periods after the first click is probably what triggers the problem.

(I'm still using beta 4.)
Sep 9, 2015  • #5
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Thanks! I haven't been able to reproduce that first issue here. Does the taskbar button stay there even after you close the Start menu?

I can reproduce the second issue, and I've added it to our list :)
Sep 11, 2015  • #6
User Image
Astaedus
7 discussion posts
No. It appears a few seconds after the start menu opens and disappears at the same time as the start menu closes.

I've attached a few screenshots.
The first one is the button that appeared when I open the start menu.
The second screenshot shows the popup that appears when I hover the mouse cursor over the button.
• Attachment [protected]: taskbar_button_1.png [19,313 bytes]
• Attachment [protected]: taskbar_button_2.png [12,652 bytes]
Sep 11, 2015  • #7
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Thanks! Would you be able to attach a debug log as well?
  • On the Troubleshooting tab, change the Logging drop-down to "L1: Log Minimal"
  • Restart DisplayFusion
  • Reproduce the issue and note the time so we'll know where to check in the log file
  • Send us the DisplayFusion.log and DebugInfo.html files (can be found by clicking the Open Log button on the Troubleshooting tab)
  • Disable debug logging after sending the log
Sep 11, 2015  • #8
User Image
Astaedus
7 discussion posts
I just upgraded from Beta 4 to Beta 6 and the blank taskbar button no longer appears.
Something you changed in Beta 5 or 6 must have fixed it.

Thank you
Sep 12, 2015 (modified Sep 12, 2015)  • #9
Subscribe to this discussion topic using RSS
Was this helpful?  Login to Vote(-)  Login to Vote(-)