Home/ Questions/Q 3362266
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-18T03:15:12+00:00

I have a VS2008 C++ application for Windows XP SP3 developed using WTL 8.1.

  • 0

I have a VS2008 C++ application for Windows XP SP3 developed using WTL 8.1. My application contains a tab control that flickers when the application border is resized.

My window hierarchy looks like this:

CFrameWindowImpl   CMainFrm
|-CSplitterWindow  Splitter
  |-CTabView       Configuration Tabs
  | |-CDialogImpl  Configuration View 1
  | |-CDialogImpl  Configuration View 2
  | |-CDialogImpl  Configuration View 3
  |-CDialogImpl    Control View

The solution I’m trying is to make the CFrameWindowImpl derived class use the WS_EX_COMPOSITED style and all windows beneath it use the WS_EX_TRANSPARENT style. Unfortunately, this makes the tab control buttons show as an empty black bar and the controls of any Configuration View to not show at all.

If I remove the WS_EX_COMPOSITED and WS_EX_TRANSPARENT styles, the form displays properly, but the CTabView and everything beneath it flickers horribly when resized.

What do I need to change to eliminate the flicker and draw the controls properly?

Thanks,
PaulH

Edit:
Got it working. I removed all the WS_EX_TRANSPARENT styles per Mark Ransom’s suggestion. I put the WS_EX_COMPOSITED style on only the CTabCtrl (contained within the CTabView). Other controls get double-buffering as needed through WTL::CDoubleBufferImpl<>.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    A window flickers because it gets erased before it’s drawn. To eliminate this you need to disable erasing of the window entirely and use double buffering – draw the window contents into a bitmap, then copy the bitmap to the window. Because the bitmap contains the entire contents including the background, there’s no need to erase anymore.

    It looks like WS_EX_COMPOSITED will handle the double buffering automatically, but you still probably need to use a NULL background brush and/or handle the WM_ERASEBKGND message.

    • 0