Tabbed Dock is big blank rectangle

Object Dock Plus 2.0 running on 64-bit Win7 Ultimate, on 2 different machines.  Same behavior on both machines.

Tabbed Dock looks normal, then turns into big blank rectangle.  You can change the theme using the Settings dialog and it resumes it's correct appearance, but within a minute goes blank again.

This is a brand new installation downloaded yesterday.

2,621 views 8 replies
Reply #1 Top

Could be the installation borked. Do an uninstall then re-install. See if that corrects the problem. If not start a trouble ticket with support.

Reply #2 Top

Can you post a screenshot of what you are seeing?

Reply #3 Top

Are you running Logitech's Setpoint on both machines? If so, does uninstalling Setpoint make the problem go away?

I'm asking this because I've run into this exact problem before - it was caused by Logitech's mouse driver software hooking into every process and sending supurious WM_PAINT messages to layered (alpha blended) windows. Only happened on x64 machines too.

Reply #4 Top

JcRabbit, you nailed it!!!

Logitech Setpoint was running.  Exiting Setpoint fixed the problem.  This was happening on two x64 machines, both running Setpoint.

Then, when I restarted Setpoint, within 10 seconds I got the blank boxes again.  

Thanks for your hint, although I'm not sure I like the fix...

 

 

Reply #5 Top

Dewie, tell Jeff Bargman about this - he will have to 'eat' WM_PAINT messages, which are sent by Setpoint, at the WndProc level for every layered window he uses in OD 2:

    Case WM_PAINT

        Dim lngExStyle As Long
        Dim ps As PaintStruct
       
        lngExStyle = GetWindowLong(hw, GWL_EXSTYLE)
       
        If (lngExStyle And WS_EX_LAYERED) Then
            Call BeginPaint(hw, ps)
            Call EndPaint(hw, ps)
            Exit Function
        End If

Logitech makes some great hardware, but their software sucks, sorry to say. Unfortunately Setpoint ships with every Logitech mouse, so *we* have to come up with work arounds for other people's bugs. Sigh.

Not the first time Winstep has been bitten by bugs in Logitech stuff either - I remember their Webcam Control Panel applet which corrupted the stack whenever Control Panel items were enumerated (to display them on a NextSTART menu or on the Shelf, for instance). Explorer was imune to this, of course, so this bug that actually caused the application to crash was, for users, a bug in *your* application, not Logitech's software. Tracking this one down, and comming up with a work-around, was definitely NOT fun.

Reply #6 Top

Jeff has been made aware of the issue, as well as this thread.

Reply #7 Top

Jc - Wow, that's wild. I do have SetPoint software and aren't running into that but believe it. Though, I am confused as to how a WM_PAINT message can make a difference. I felt that WM_PAINTs just don't have effect on layered windows.

 

As a matter of fact though, I do eat WM_PAINT's with a ValidateRect (should do the same job i imagine) for my dock item windows (e.g. zooming docks), but not cabinets (tabbed docks). Funny. Will make note to put in that compatibility bit.

 

Btw, that sounds horrible with the control panel situation! I know the feeling. Anyhow thanks for the tip :)

Reply #8 Top

Quoting JMBdev, reply 7
Jc - Wow, that's wild. I do have SetPoint software and aren't running into that but believe it. Though, I am confused as to how a WM_PAINT message can make a difference. I felt that WM_PAINTs just don't have effect on layered windows.
End of JMBdev's quote


Yes, they shouldn't have any effect, but, if you don't do this, Windows will assume that the window is still invalid and pump another WM_PAINT. It does this over and over, flooding the input queue and causing the window to stop refreshing. Apparently the MSDN Knowledge Base page that mentioned this issue no longer exists, either.

Quoting JMBdev, reply 7
Btw, that sounds horrible with the control panel situation!
End of JMBdev's quote

It was. First it took a very long time to figure out the common denominator between users suffering from this problem, then I actually had to buy a Logitech web cam to understand exactly what was happening and be able to work around it. The good news is that I'm still using that web cam, even though this happened years ago. :)

Quoting JMBdev, reply 7
Anyhow thanks for the tip
End of JMBdev's quote

Glad I could help!