Saito S
19 discussion posts
Ahoy! I'm not sure if this specific issue has been discussed here before; a quick search didn't yield anything relevant that I noticed. At some point after a recent-ish update (maybe for a few months now), DisplayFusion has become very, very slow. By "DisplayFusion", I mean USING it actively. Swapping windows to different monitors, activating existing wallpaper profiles, etc. are all about the same as they always were, but actually opening the DisplayFusioin interface to actually make any changes is incredibly slow. This is especially noticeable when using the "Desktop Wallpaper" section. After working within this window for a few minutes (say, creating a couple new wallpaper profiles), most functions become unbearably slow. If I click on, for example, the up/down arrows in the "Adjustments" section, it can take almost 10 seconds for a single click to actually register and the scale adjustment to appear - needless to say, this makes it so making several fine adjustments is a maddening process that drags on as I wait for each click to register. Almost EVERY function in various menus is like this, though some are much worse than others.
At one point when it seemed particularly bad, I decided to just close the window, give it a second, and reopen it to see if that would help. Well that was the wrong move as it turned out - once I had reopened Desktop Wallpaper, it took over thirty seconds before a click on ANY button or function anywhere in the window would register at all.
Any idea what gives here? Thanks!
Nov 13, 2022 (modified Nov 13, 2022)
•
#1
TromboneFreak
1 discussion post
Same here!
Windows 10, Pro 9.9
Saito S
19 discussion posts
So I forgot to come back here and update the thread after trying the 10.0 Beta version, but I did so at the end of last week, and I am happy to report that it does indeed seem to have solved the issue! Everything is much faster now. If I make several changes in a row to a wallpaper profile, things get a little sluggish partway through, but nowhere near what was happening before (the delays I have to deal with now are like... maybe 2-3 seconds after clicking on something, whereas before it was routinely over 10 seconds and sometimes 30, etc.).
So thanks much Keith Lammers for suggesting that!
No worries, glad to hear it!