Title

Message

Confirm

<< DiscussionsReply

Bringing windows up from taskbar show up behind other windows

Avatar from Gravatar.com
alba0
9 discussion posts
When trying to bring up a minimized application from taskbar, that application will draw behind any active ones. As though the active ones are 'always-on-top'. I can only get the windows to come up properly after clicking on the icons multiple times until it decides to draw correctly after multiple attempts.

This is affecting both the regular taskbar and the displayfusion taskbar. It is fixed by killing the displayfusion task and starting it again. Is there a solution to this?

Also, is there a displayfusion refresh or restart button? Killing the task and opening it again.. is tedious.
Jan 28, 2020 (modified Jan 28, 2020)  • #1
Avatar from Gravatar.com
alba0
9 discussion posts
Bump?

This hasn't happened before in previous versions. Workflow is so bad I had to turn off Displayfusion for now. Shame.
Jan 31, 2020  • #2
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Could you send me a copy of your troubleshooting info? Here are the steps:

  • Open the Settings > Troubleshooting tab
  • Click the "Export Info to File" button
  • Reply with the file attached
Jan 31, 2020  • #3
Avatar from Gravatar.com
alba0
9 discussion posts
attached
• Attachment [protected]: DisplayFusionDebugInfo.zip [30,092 bytes]
Jan 31, 2020  • #4
Keith Lammers (BFS)'s profile on WallpaperFusion.com
If you enable this option in the Settings > Advanced Settings, then restart DisplayFusion, does that make any difference?

"Troubleshooting: SetWindowPos: Disallow TopMost Calls"
Feb 3, 2020  • #5
Avatar from Gravatar.com
alba0
9 discussion posts
It takes time for it to occur so I will try it and report back. Thanks.
Feb 3, 2020  • #6
Avatar from Gravatar.com
alba0
9 discussion posts
I haven't gotten the issue in a full day.

Any particular reason why that option bit would be necessary after all this time?
Feb 5, 2020  • #7
Keith Lammers (BFS)'s profile on WallpaperFusion.com
There's some weird thing with Windows 10 where using topmost calls under certain circumstances will cause this to happen. I thought we had all of our topmost calls re-written to prevent this, but maybe there's still one we missed somewhere. I will pass this over to our devs to review.
Feb 5, 2020  • #8
Was this helpful?  Login to Vote  Login to Vote
<< DiscussionsReply