Forum

Sorry for the previous test message. I had to test since I tried to post with the real problem, it did not work and I lost the posting (which was quite long). Here is my second attempt to report my problem.

I am trying to create a test MDI application in NET that will take advantage of the ResizablePropertySheet in a DialogBar. I am using a blank classwizard generated app and I am injecting parts (to be exact almost all) of the code, found in the "ResizableChildSheet" example that comes with the 2.22 freeware version of the lib.

Everything seems to be working just fine. Except one thing. When building in debug and executing I allways get the following:

First-chance exception at 0x7196211e in MDIFocus.exe: 0xC0000005: Access violation writing location 0x009ee43c.
Warning: CMDIFrameWnd without a default menu.

Pressing "Continue", at that point, the program seems to be running witout any other apparent problem.

It looks like I am missing something, but no matter how many times I looked into my code I cannot find anything wrong.

Any one with similar experiences ???

I am even willing to email the code in a zip file to anyone interested to take a look and (perhaps) provide some help.


Warm regards

Dear Sergiy

Just found that the "Warning: CMDIFrameWnd without a default menu." appears even in your sample !!! It looks like that it is totally un-related to the "First-chance exception at 0x7196211e in MDIFocus.exe: 0xC0000005: Access violation writing location 0x009ee43c."

The exception appears at the point the following is executed
CExtResizablePropertySheet::Create(pWndParent, WS_CHILD | WS_VISIBLE, 0)
in the Create( CWnd * pWndParent ) of CExtChildResizablePropertySheet.

It returns TRUE fowever the exception occurs.

Unless you have an idea why this is happening, I will email the code as you suggested. Just cleaning it up a little bit, to avoid sending over other un-related code.

Warm regards


Pothitos M. Baikas

Hi,

The "Warning: CMDIFrameWnd without a default menu" message is not critical for Prof-UIS-based apps because menu bar kills frame menu and handles all the WM_MDI*** messages.

The access violation happened in your project is an internal exception inside the PropertySheet() function call. It is handled and function returns valid HWND of the property sheet window. Exception happens when code tries to write memory with data which has format of DLGTEMPLATE-like header with followed control-description chunks. The enigma is why it never happens in the ResizableChildSheet sample? I need some time to find the source of this problem. Additionally I must note resizable child sheet as WS_CHILD window is our experimental work and I didn’t come across with this kind of property sheet anywhere before.

Best regards, Sergiy.

Dear Sergiy

Just found that the "Warning: CMDIFrameWnd without a default menu." appears even in your sample !!! It looks like that it is totally un-related to the "First-chance exception at 0x7196211e in MDIFocus.exe: 0xC0000005: Access violation writing location 0x009ee43c."

The exception appears at the point the following is executed
CExtResizablePropertySheet::Create(pWndParent, WS_CHILD | WS_VISIBLE, 0)
in the Create( CWnd * pWndParent ) of CExtChildResizablePropertySheet.

It returns TRUE fowever the exception occurs.

Unless you have an idea why this is happening, I will email the code as you suggested. Just cleaning it up a little bit, to avoid sending over other un-related code.

Warm regards


Pothitos M. Baikas

Hi,

Some time ago I wrote an MDI application with standard menu line at the top of the frame (not using Prof-UIS menu bar) which contain only one popup submenu item. I noticed MFC code supposes MDI frame menu should have at least two popup items because it uses second popup submenu at right side to append MDI windows commands (Window1, Window2 . . . Window9, More Windows). Please verify your frame has menu with at least two popup items and the second item at right side is submenu.

Of course, it will be interesting to take a look at your project and find out the source of the problem. You can e-mail it to l_sergiy@fossware.com.

Best regards, Sergiy.