oleg wrote: We agree, that we added this problem in 9.60.1 :(

No problem, Oleg, thanks for releasing 9.60.1 all the other new fixes/features were well worth the hassle of tracking down that problem.  Keep up the great work...

JamesH, please make something liek

if (Control->Caption != Caption)

{

Control->Caption = Caption;

}

We agree, that we added this problem in 9.60.1

:(

I reviewed the code in our commandbars update handler and the flashing is caused by assigning a value to the controls Caption member.

Again, this only happens in 9.60.1 it was fine in 9.60 ... I have hacked together a sample that shows the problem.  This is basically a melding of your two WTL samples.

You can see in the update handler I re-assign the caption of each control, this is what causes the flashing.

2005-03-10_124406_Copy_of_WTLSample.zip

It can be only if you update some states of commandbars in update handler.

Try to comment your Update function.

May be you can attach your Frame code?

** Update 2 - Potential fix? **

Since I was also seeing several WM_TIMER messages coming into the pane dialogs, on a whim, I set the UpdatePeriod on the command bars object to 10,000 and this slows down the flashing.  The re-paint flashing is tied to the UpdatePeriod, if I incrase the update period the flashing slows down if I decrease it the flashing speeds up.  (This only happens with the 9.60.1 version of the docking pane)

Any ideas why or how I can continue to use the comand bars update timer but not have my panes flash?

** Update **

I added a call on the child window that is displayed in the docking panes (the ones that are being repainted) and it is getting a stream of these messages:

WM_SIZEPARENT       0x0361

WM_WINDOWPOSCHANGING      &nbs p;     0x0046

(I'm not sure what message 0x0486 is)

Here is the trace, the number in brackets is the address of the dialog, followed by the message number in decimal and hex.

 DockPaneDialog (208651312) msg: 865, 361h
 DockPaneDialog (208647208) msg: 865, 361h
 DockPaneDialog (208645448) msg: 865, 361h
 DockPaneDialog (208643912) msg: 865, 361h
 DockPaneDialog (208641504) msg: 865, 361h
 DockPaneDialog (208638896) msg: 865, 361h
 DockPaneDialog (208620880) msg: 865, 361h
 DockPaneDialog (208612648) msg: 865, 361h
 DockPaneDialog (208598760) msg: 865, 361h
 DockPaneDialog (208606368) msg: 1158, 486h
 DockPaneDialog (208606368) msg: 70, 46h

If the only change I make is to use version 9.6 I don't see those messages passed to the child window.  When I switch back to 9.60.1 I get a constant stream of those messages.   Which causes the windows to repaint over and over.

Any ideas where those messages could be coming from?

oleg wrote: When they flash?

They flash constantly anytime two panes are docked.  If I only have one pane displayed or the other panes are tabbed or floating they do not flash.

Each pane is receiving a non stop series of WM_PAINT messages.

The problem does not exist with the WTL sample so is likely due to some of the obscure message handling I do with the underlying panes.  I trap specific messages for various reasons (such as determining which pane is the active pane).

As this was not a problem with the previous (9.60) version I was wondering if anyone had any ideas what areas have changed in 9.60.1 so it would give me an idea of where to start looking (debugging paint messages is always a pane)...