ZMuerte
12 discussion posts
seems like an exploit waiting to happen if you ask me. anyways: when locking the computer, most of the time, the DF taskbars will stay there for a few seconds. sometimes when waking from sleep the taskbars are there on the lockscreen as well. clicking on the icons works, and shows a quick flash of the desktop on non-primary monitors.
a different small issue I have: if I have wallpapers change with a transition, it goes through the transition fine, but right as it's supposed to settle into the 2nd wallpaper, it flashes the first one for a frame, then goes to the 2nd wallpaper.
Yeah, we've done our best to detect the lock screen and disable the taskbars, but it's not always reliable for some reason. It shouldn't even be possible for an application to put itself in front of the lock screen, as this indeed can be a huge security issue. Imagine if someone wrote a password overlay to sit on the lock screen, causing you to enter your password so they can capture it. We reported the issue to Microsoft but never heard back.
Regarding the desktop wallpaper, I can't reproduce that here on any of my test machines. Have you tried updating your graphics drivers? Also, do you have any other applications that modify the desktop at all?
ZMuerte
12 discussion posts
nevermind on the transition error. It doesn't seem to happen anymore (honestly, it happened when I first got win10, so I turned off transitions. never turned them back on). it may be due to the newest version (which fixed a bunch of little nitpicks I had with it), but I'm not sure.
After watching it for a bit, it seems to jump every so often. it's not every single change anymore, but more like every 7 or so (I have it set to a very rapid change speed because I don't want it just sitting there).
Geforce Experience reports that I'm using the latest drivers. Intel drivers seem to update through windows update.
AFAIK: no other programs should be modifying the desktop.
I know, it makes it quite difficult to debug when it's not exactly consistent or anything. Could it have a similar problem as the memory leak, as I do have my wallpaper set to load every 0.1 minutes?
Suppose it would be a good idea to add a debug log or something.
• Attachment [protected]: DisplayFusion.log [240,017 bytes]
• Attachment [protected]: troubleshooting.txt [94,466 bytes]
Aug 22, 2015 (modified Aug 22, 2015)
•
#3