It still doesn't look like I am destroying the CDockable Panel correctly. I am getting some very wierd responses. I'll try to list all of the occurances I'm noticing, perhaps somebody will see something: 1. When a CDockablePanel is docked and I hit the 'X' button, the window disapears and memory and thread is cleared,which is the desired action, however it looks like there is a base control

On May 2, 5:03 pm, Nick Schultz <NickSchu...@discussions.microsoft.com> wrote: OK, I tried overriding both PostNcDestroy and OnPressCloseButton functions and it still isn't working the way I would like it to... When I create the window, it starts out docked to the main frame. If I undock the window and then close it, those functions do not get called. If I leave it docked, or undock

OK, I tried overriding both PostNcDestroy and OnPressCloseButton functions and it still isn't working the way I would like it to... When I create the window, it starts out docked to the main frame. If I undock the window and then close it, those functions do not get called. If I leave it docked, or undock it and dock it again and then close the window, those functions get called.

This is not a good description. If DoModal "fails", it will return 0. If it succeeds, you should see a dialog box. Presumably you are going to fill in all those parameters at some point, because you are using the defaults, so there is no reason to provide default parameters to the constructor. I see no function f() here. What version of VS are you using, what platform SDK, what OS?

I am encountering a wierd error, and I can't figure out which way to turn. Something deep within the call tree of CFileDialog::DoModal() is (apparently) failing, causing the dialog to never be displayed, and the f() never to return. Here's the failing code: void CPvtDlg::OnBnClickedBnFileBd() { // specify a file CFileDialog fileOpenBox ( TRUE,