yes i think the wizard for 6 and 7 both have the option to start yourp roject like that too otherwise you create the splitters in CMainFrame::OnCreateClient there is some example code how to do it in the msdn info on CSplitterWnd also

i seem to get this warning on damn near any MFC project i've used on Visual Studio .net LINK : warning LNK4089: all references to 'OLEAUT32.dll' discarded by /OPT:REF i looked it up and apparently the linker is decided that i dont need OLEAUT32.dll cause nothing is using it.. but i cant figure out where in the world any part of my project is mentioning OLEAUT32.dll in the first place. so im not sure why the linker thinks i wanted it in the first place

i have generally heard adding WS_CLIPCHILDREN to a parent window reduces flicker and i couldve sworn it has worked for me like that in the past but im writing an MFC application, it has a main frame tab control, and in the tabbable area i have a splitter with scrollable dialog views in it. weirdest thing is, if the mainframe has WS_CLIPCHILDREN the Tab control flickers like crazy on resizing (mostly grey while sizing) but without it it barely flickers at all (still flickers some) (also i changed the behavoir for OnSize to not make the splitter fill the whole frame area, cause i think this was causing flicker also because i would just immediately resize the splitter back into the tab controls display area) similarly i noticed that if my CSplitterWnds are created with WS_CLIPCLILDREN then whenever any part of the frame is resized ALL the child panes have TERRIBLE flickering but when i take WS_CLIPCHILDREN back off of the splitters i have very minimal flickering (just like on the main tab control) i dont understand why having WS_CLIPCHILDREN on Frames and Splitters would cause so much more terrible flicking for their child windows