// If there a list of bitmap id's, then let the user configure the toolbar
if (m_pBitmapIds != NULL)
dwStyle |= CCS_ADJUSTABLE;
// initialize common controls
// save the style,Please Add the follow line here
SetBarStyle(dwStyle & CBRS_ALL);
// create the HWND
if (!CWnd::Create(TOOLBARCLASSNAME, NULL, dwStyle, rect, pParent, nID))
Basically the fix is to insert "SetBarStyle(dwStyle & CBRS_ALL) right before you call the
CWnd::Create method. For the curious of you, the reason that this crash occurs in the first place, is that
Microsoft, in their infinite wisdom, decided to insert additional checking in the create method, in
particular, asserting that the dwStyle long contains only MFC-defined flags, and not any user-defined flags.
VC5 did not do this, that's why it doesn't crash. If you go to Search in the VC6.0 IDE, and type in CBRS_ALL,
the only link that comes up is where they mention this additional checking.
Now, when I applied those fixes, I got a different crash. (Duh) In this case, it was something in
winfrm2.cpp, whatever that is. Anyway, that's fixed by commenting out the following lines, like so:
I'm not sure if it is related to the dockable windows'.... but in the Dockdemo sample there is a noticeable
flicker in the tab control when we change between tabs.....any idea why and how do we eliminate it....
Not entirely sure how I did it, but I re-downloaded the mrcext50.zip file, unzipped, and did a rebuild all
for the debug version of the mrcext project with VC 6.0. Copied the .lib and .dll files over to my other
project directory. Removed all the old references to the MRCEXT/VC 4.0 version (lib, and header files) and
added references to the new MRCEXT/VC 5.0/6.0 version. Did a rebuild all on my app and the debug
assertion/crash went away.