Since I did the automatic update to V3.1.2, my wallpapers aren't automatically updating any longer. Also, my Hotkey (Control+3) to switch to the next set of wallpapers, doesn't work either. If I open up the "Desktop Wallpaper" config option, click "Apply" or "OK", the papers will update that one time. But they won't update automatically or via the Hotkey.

Matt Dralle

I've tried uninstalling and reinstalling V3.1.2, and also installing V3.0.6 but my papers still won't update. I have a system with 6 1920x1200 monitors and have different wallpapers per-monitor. I am running Vista 64. Its been working great up until the 3.1.2 upgrade.

I have attached my Binary Fortress Registry Tree and also a DisplayFusion.log file for reference.

I tried shutting down DF and deleteing the registry tree, forcing DF to create a new one. This didn't change any of the symptoms.

I have Control+3 set as the Next Wallpaper hotkey. This also used to work, but now doesn't do anything.

Help!

Matt Dralle

[Edit: I have removed your .reg file, as it contained your license key.]

Can you take a screenshot of your desktop wallpaper window?

See attached...

The only thing I can think of is the file path being too long. And what are those pics of if you don't mind me asking?

Thanks for the test code, Jon. I installed it and have included a copy of the log file.

However, I have figured out what is causing the problem, sort of. Seems that if I have the Setting "Don't check for wallpaper changes while a full screen application is running" checked, it will never update the wall papers. If I uncheck this option, then it updates as expected. There are no full screen options running on my system, so DF must be mistakenly detecting a FS app for some reason.

At the end of the attached log file, you'll see a number of "HotKey Pressed: Next random wallpaper..." entries. I have the "Don't Check during FS" option checked during these and no updates are occuring. An interesting debug might be to have DS output what app it thinks is running full screen during these update request/times.

Matt Dralle

With the test version installed and the "don't update with fullscreen app..." option enabled (and no updates occuring and no fullscreen app running), here is the troubleshooting info:

--- Machine ------------
Operating System: Microsoft Windows NT 6.0.6001 Service Pack 1
Operating System Version: 6.0.6001.65536
Detected Version: WindowsVista / 2008
CPU: x64
Date/Time (UTC): 09/08/2009 05:17:49
Date/Time (Local): 09/07/2009 22:17:49
.NET Framework: 2.0.50727.1434
CurrentCulture: English (United States) (en-US ~ en)
CurrentUICulture: English (United States) (en-US ~ en)

--- Wallpaper ------------
Wallpaper Span: False
Monitor #1 Image: D:\Ricci\Various Pictures\Collection A\Various Pictures I (6307).jpg (Exists: True)
Monitor #2 Image: D:\Ricci\Various Pictures\Collection A\Various Pictures I (729.jpg (Exists: True)
Monitor #3 Image: D:\Ricci\Various Pictures\Collection A\Various Pictures I (17).jpg (Exists: True)
Monitor #4 Image: D:\Ricci\Various Pictures\Collection A\Various Pictures I (6123).jpg (Exists: True)
Monitor #5 Image: D:\Ricci\Various Pictures\Collection A\Various Pictures I (314.jpg (Exists: True)
Monitor #6 Image: D:\Ricci\Various Pictures\Collection A\Various Pictures I (677).jpg (Exists: True)
Windows Wallpaper: C:\Users\dralle\AppData\Roaming\DisplayFusion\Wallpaper_2.jpg (Exists: True)
Generated Wallpaper Folder: C:\Users\dralle\AppData\Roaming\DisplayFusion

--- DisplayFusion ------------
Name: DisplayFusion Pro v3.1.2
Build Date: Sep 07, 2009 23:24
Pro: True
Pro License: 101-WZHN-E62B-XWHO (truncated)
Command Line: "C:\Program Files (x86)\DisplayFusion\DisplayFusion.exe"
Current Folder: C:\Program Files (x86)\DisplayFusion
Performance Mode: False
Mouse Hooks: True
Application Hooks: True
System Hooks Pause FullScreen: False
Process Integrity Level: High

--- DisplayFusion x86 Hook DLL ------------
Path: C:\Program Files (x86)\DisplayFusion\DisplayFusionHookx86.dll
Name: DisplayFusion Hook
Prod Version: 1, 9, 0, 0
File Version: 1, 9, 0, 0
Size: 48,304 bytes

--- DisplayFusion x64 Hook DLL ------------
Path: C:\Program Files (x86)\DisplayFusion\DisplayFusionHookx64.dll
Name: DisplayFusion Hook
Prod Version: 1, 9, 0, 0
File Version: 1, 9, 0, 0
Size: 60,080 bytes

--- DisplayFusion x86 Hook Exe ------------
Path: C:\Program Files (x86)\DisplayFusion\DisplayFusionHookx86.exe
Name: DisplayFusion Hook x86
Prod Version: 1, 3, 0, 0
File Version: 1, 3, 0, 0
Size: 92,848 bytes

--- Monitor 1 (Primary:True ~ Real:True) ------------
Name: \\.\DISPLAY1
Bounds: {X=0,Y=0,Width=1920,Height=1200}
WorkArea: {X=0,Y=0,Width=1920,Height=1200}

--- Monitor 2 (Primary:False ~ Real:True) ------------
Name: \\.\DISPLAY2
Bounds: {X=1920,Y=0,Width=1920,Height=1200}
WorkArea: {X=1920,Y=0,Width=1920,Height=1200}

--- Monitor 3 (Primary:False ~ Real:True) ------------
Name: \\.\DISPLAY3
Bounds: {X=-1920,Y=0,Width=1920,Height=1200}
WorkArea: {X=-1920,Y=0,Width=1920,Height=1200}

--- Monitor 4 (Primary:False ~ Real:True) ------------
Name: \\.\DISPLAY4
Bounds: {X=0,Y=-1200,Width=1920,Height=1200}
WorkArea: {X=0,Y=-1200,Width=1920,Height=1200}

--- Monitor 5 (Primary:False ~ Real:True) ------------
Name: \\.\DISPLAY5
Bounds: {X=-1920,Y=-1200,Width=1920,Height=1200}
WorkArea: {X=-1920,Y=-1200,Width=1920,Height=1200}

--- Monitor 6 (Primary:False ~ Real:True) ------------
Name: \\.\DISPLAY6
Bounds: {X=1920,Y=-1200,Width=1920,Height=1200}
WorkArea: {X=1920,Y=-1200,Width=1920,Height=1200}

--- Screens ------------
Count: 6
Point Min X: -1920
Point Min Y: -1200
Point Max X: 3840
Point Max Y: 1200
Total Width: 5760
Total Height: 2400
ActiveDesktop: False

--- Screen 1------------
ScreenID: 0
Device: \\.\DISPLAY1
Bounds: {X=0,Y=0,Width=1920,Height=1200}
MoveH: 0
MoveV: 0

--- Screen 2------------
ScreenID: 1
Device: \\.\DISPLAY2
Bounds: {X=1920,Y=0,Width=1920,Height=1200}
MoveH: 0
MoveV: 0

--- Screen 3------------
ScreenID: 2
Device: \\.\DISPLAY3
Bounds: {X=-1920,Y=0,Width=1920,Height=1200}
MoveH: 0
MoveV: 0

--- Screen 4------------
ScreenID: 3
Device: \\.\DISPLAY4
Bounds: {X=0,Y=-1200,Width=1920,Height=1200}
MoveH: 0
MoveV: 0

--- Screen 5------------
ScreenID: 4
Device: \\.\DISPLAY5
Bounds: {X=-1920,Y=-1200,Width=1920,Height=1200}
MoveH: 0
MoveV: 0

--- Screen 6------------
ScreenID: 5
Device: \\.\DISPLAY6
Bounds: {X=1920,Y=-1200,Width=1920,Height=1200}
MoveH: 0
MoveV: 0

--- Managed Threads ------------
Count: 2
ID:3 ~ Name:HookManager ~ Age:00:01:54.9980000 ~ Alive:True ~ BG:True ~ State:Background ~ Thread Name:HookManager_5a73e38a-dd1f-42f6-aa6c-a3499668f31a
ID:4 ~ Name:HookManagerProcess ~ Age:00:01:54.9240000 ~ Alive:True ~ BG:True ~ State:Background ~ Thread Name:HookManagerProcess_217c0680-2b70-45ec-b89c-54c78c030c9b

--- Taskbars ------------
Enabled: False
Auto-hide: False
Visual Styles: True
Visual Styles Detected: False
DWM Composition Detected: False
Opacity: 100
Flash Blink: True
Window Options: ShowRelevant
Button Width Max: 160
Sizing Bar Size: 8
Full Screen: 0003062e ~ {X=1920,Y=-1200,Width=1920,Height=1200} ~ "Xenia VNC Console", 00010686 ~ {X=-1920,Y=-1200,Width=1920,Height=1200} ~ "Roxy VNC Console"

--- Taskbar Items ------------
"DisplayFusion Pro ~ Settings" (00091da8:00091da8:00091da8 ~ None ~ {X=2504,Y=351,Width=751,Height=498})
"DisplayFusion" (000612d2:000612d2:000612d2 ~ None ~ {X=2781,Y=686,Width=714,Height=487})
"Post reply - Windows Internet Explorer" (00100148:00100148:00100148 ~ None ~ {X=291,Y=19,Width=1007,Height=1172})
"KitLog Pro - My KitLog - Windows Internet Explorer" (000404a4:000404a4:000404a4 ~ None ~ {X=0,Y=-1200,Width=1169,Height=1200})
"Xenia VNC Console" (0003062e:0003062e:0003062e ~ None ~ {X=1920,Y=-1200,Width=1920,Height=1200})
"Computer" (000200a4:000200a4:000200a4 ~ None ~ {X=-1821,Y=3,Width=239,Height=528})
"Roxy VNC Console" (00010686:00010686:00010686 ~ None ~ {X=-1920,Y=-1200,Width=1920,Height=1200})
"Matt's Complete Audio CD Library - Windows Internet Explorer" (0001101e:0001101e:0001101e ~ None ~ {X=1168,Y=-1200,Width=752,Height=765})
"Winamp 5.552" (000107d0:000107d0:000107d0 ~ Winamp ~ {X=1170,Y=-435,Width=275,Height=116})
"Eudora" (00011374:00011374:00011374 ~ None ~ {X=115,Y=55,Width=1728,Height=1081})
"Eudora" (000118e2:000118e2:000118e2 ~ None ~ {X=90,Y=53,Width=1728,Height=1092})
"Eudora" (000116c6:000116c6:000116c6 ~ None ~ {X=103,Y=59,Width=1728,Height=1091})
"606-6281 - Telephone Caller ID Display - Version 1.5.2" (00010ade:00010ade:00010ade ~ None ~ {X=1921,Y=905,Width=646,Height=295})
"606-1001 - Telephone Caller ID Display - Version 1.5.2" (00010a04:00010a04:00010a04 ~ None ~ {X=1921,Y=609,Width=646,Height=295})
"447-9886 - Telephone Caller ID Display - Version 1.5.2" (0001094c:0001094c:0001094c ~ None ~ {X=1921,Y=313,Width=646,Height=295})
"XtreMe PCR" (00010700:00010700:00010700 ~ None ~ {X=1444,Y=-436,Width=476,Height=436})
"VOICEMAIL" (000106b2:000106b2:000106b2 ~ None ~ {X=316,Y=74,Width=1288,Height=1051})
"Eudora" (000115f8:000115f8:000115f8 ~ None ~ {X=107,Y=55,Width=1728,Height=1092})
"Eudora" (000117e2:000117e2:000117e2 ~ None ~ {X=96,Y=60,Width=1728,Height=1080})
"Eudora" (000119d2:000119d2:000119d2 ~ None ~ {X=99,Y=48,Width=1728,Height=1093})
"Eudora" (00031334:00031334:00031334 ~ None ~ {X=100,Y=56,Width=1729,Height=1083})
"Kara VNC Console" (0001063c:0001063c:0001063c ~ None ~ {X=0,Y=-1200,Width=1920,Height=1200})
"Kitlog VNC Console" (0001064e:0001064e:0001064e ~ None ~ {X=0,Y=-1200,Width=1920,Height=1200})
"Eudora" (000a0882:000a0882:000a0882 ~ None ~ {X=88,Y=82,Width=1728,Height=1064})
"Desktop Manager" (000206e4:000206e4:000206e4 ~ None ~ {X=2065,Y=681,Width=800,Height=519})

--- TitleBar Buttons ------------
Enabled: False
DisplayFusion Caption Button Size: {Width=18, Height=18}
System Caption Button Size: {Width=18, Height=18}

Ah! Those are remote-desktop-like sessions I have to other computers. I have them running on two of the displays - in full screen mode. Duh. I didn't think about the fact that on a multi-display system, "full screen" doesn't exactly mean the same thing as it does on a single display system.

What's curious is why did it start inhibiting the updates with the latest upgrade?

Matt Dralle

hey, on a positive note - now you know, Jon, that your FS application detection is working correctly - or, at least, better than it was before....

And thats the lesson of the day. lol.. Just good to know its not something actually bad.

Jon,

Things continue to work as advertized. As far as the full-screen detection, I'm wondering if the logic should take into account mulit-display setups. "Fullscreen" really isn't possible with multiple displays. Maybe the option should be grayed out on systems with multiple displays....?

Matt