Processing Ajax...

Title
Close Dialog

Message

Confirm
Close Dialog

Confirm
Close Dialog

Confirm
Close Dialog

User Image
Randy31416
19 discussion posts
On one of my monitors I have static windows carefully placed. On that monitor I have disabled the DF taskbar, and it does not show. Yet every now and then, and especially after suspend and resume, DF has pushed the windows upward to make space for the taskbar that it is not going to show. Is there some way to stop this happening?
Nov 10, 2015  • #1
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Could you attach a copy of your troubleshooting info? I'd like to test this out here.
  • Open the Settings > Troubleshooting tab
  • Click the "Copy to Clipboard" button
  • Paste the text into a text file (please don't paste the text directly into your reply, the formatting gets garbled and makes it difficult to parse)
  • Reply with the file attached

Thanks!
Nov 11, 2015  • #2
User Image
Randy31416
19 discussion posts
The file is attached. I did actually see the pushup occur today as it occurred, and what I saw was the start button icon drawn in its normal position, but nothing else drawn (all this on a monitor with the taskbar disabled). Subsequently I also disabled the start button on that taskbar, but the push-up still occurs. The push-up does not occur on every suspend and resume, only some, and I cannot isolate anything distinctive to distinghish the two cases.

Note that I use Classic Shell. Monitors 3 and 4 have the taskbar disabled; Monitor 4 is the one that has the other windows on it that get pushed up (Monitor 3 ususally has nothing in the area that would get pushed).

Thanks for your interest.
• Attachment [protected]: DisplayFusionTroubleShootReport.txt [84,835 bytes]
Nov 12, 2015  • #3
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Thanks Randy! It definitely sounds like DF starts to setup the taskbar on that monitor, even though it shouldn't be. Would you be able to send over a full debug log? Here are the steps:
  • 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
Nov 13, 2015  • #4
User Image
Randy31416
19 discussion posts
OK, I have done this. I ran for a long while, forgetting that I had turned off taskbars altogether so that the windows did not get pushed around. Then this mornng, I reenabled the taskbars, put a pushable window on monitors 3 and 4, disabled thte taskbars on monitors 3 and 4, and did a suspend-resume. Both monitors got a taskbar (for a brief while) and both of my windows got pushed.

The resume occured at "2015/11/14 04:23:00", and in the DisplayFusion.log shortly thereafter are lots of setup actions for Taskbar7 and Taskbar8 on the relevant monitors (X from -1200 to 0000 is monitor 3 and X from 2560 to 3760 is monitor 4).

Good luck.
• Attachment [protected]: DebugInfo.html [130,362 bytes]
• Attachment [protected]: DisplayFusion.log [3,186,198 bytes]
Nov 14, 2015  • #5
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Thanks Randy! We'll check it out :)
Nov 17, 2015  • #6
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Wow, that's really weird! I wonder where it's getting monitor IDs 7 and 8 from. If you create these two registry values, does this issue still occur?

Key: HKEY_CURRENT_USER\Software\Binary Fortress Software\DisplayFusion\Taskbars\7
Value Type: String (REG_SZ)
Value Name: Position
Value Data: 100

Key: HKEY_CURRENT_USER\Software\Binary Fortress Software\DisplayFusion\Taskbars\8
Value Type: String (REG_SZ)
Value Name: Position
Value Data: 100
Nov 18, 2015  • #7
User Image
Randy31416
19 discussion posts
Neither Taskbar7 nor Taskbar8 had the Position value (as I guess you know) so I have added them and we will see what happens over time. For testing, two quick suspend-resumes did not result in the pushup, and the taskbars were not seen.

When I look at my display configuration, reading it with EnumDisplayDevices, I find 12 montors (two sets of 6). Attached is a screen shot of the list. I've never understood why and never understood the numbering that I see. Sometimes I see numbers 1 through 4 (at least I used to in an older installation) and sometimes I see 1,2,7,8. This is a fresh install of Windows 7 x64 from a month or so ago. My screen configuration does change from time to time through another program, sometimes down to a single screen (monitor 1 or 2), sometimes to monitor 1 plus 7 and 8, and sometimes to all four. The Radion HD7700 cards each have two DVI outs (what I use), an HDMI out, and a display port out (and I think diplay ports allow daisy-chaining to length 3). I wonder if those unused possibilities are what is enumerated. Just did a fresh reboot, and the monitor numbers are 1,2,7,8.

Assuming the taskbars don't pop up again, maybe we'll never need to know why the numbering is weird.
Nov 18, 2015  • #8
User Image
Randy31416
19 discussion posts
Whoops -- attached here is the monitor list. And this morning there was no window pushup on the two monitors with disabled taskbars.
• Attachment [protected]: monitor list.png [34,106 bytes]
Nov 19, 2015 (modified Nov 19, 2015)  • #9
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Yeah, that's really weird! You shouldn't run into that issue any more after creating those values. It seems like the monitors are enumerating as 7,8 for some reason, so they weren't using the settings for taskbars 3 and 4. Then they update to 3 and 4 again, and the taskbars get removed. Now that you've got settings in the registry for both sets of monitor IDs, that should cover both scenarios :)
Nov 20, 2015  • #10
User Image
Randy31416
19 discussion posts
I have not seen the windows get pushed up for a while, now, over many suspends and resumes, so I think this is fixed. Now, if I just remember the fix the next time I reinstall windows . . . .

Thanks.
Nov 22, 2015  • #11
Subscribe to this discussion topic using RSS
Was this helpful?  Login to Vote(-)  Login to Vote(-)