C / C++ / MFC

How to dynamically modify menu in MDI app

14-Aug-01 7:24

Use GetVolumeInformation.

Tomasz Sowinski -- http://www.shooltz.com

JerzyPeter14-Aug-01 6:26

14-Aug-01 6:26

Hello everybody!

I´m writing a MDI app. Application Wizard generates two menus:

One (IDR_MAINFRAME), which is displayed when no document is open, the other (IDR_XXXTYPE) when there is at least one document opened.

This code below (from CMainFrame::OnCreate) modifies the first menu. I want to do the same modification to the other menu.

How to do that?

Thank you for any comments.
Jerzy

CMenu PopupMenu;
PopupMenu.CreateMenu();

for(int i=0;i<3;i++)
{
CString str;
str.Format("Item %d",i);
PopupMenu.AppendMenu(MF_STRING,IDM_ITEM+i,str) ;
}

CMenu *m=GetMenu();
m->AppendMenu(MF_POPUP¦MF_STRING,(UINT)PopupMenu.m_hMenu,"&Items");
PopupMenu.Detach();

Not Active14-Aug-01 7:01

Not Active

14-Aug-01 7:01

Use GetSubMenu to get the proper menu and continue as you have been.

JerzyPeter14-Aug-01 9:39

14-Aug-01 9:39

Hi,

I don't know what you mean to use GetSubMenu()?

This code is working, it ataches a new popup to the main menu.

The problem is that it ataches this submenu to the IDR_MAINFRAME menu (after main frame is created). I need to do the same for IDR_VIEWTYPE menu. I don't know in what moment that menu is created. If I use this code in that moment, the new popup would be attached to IDR_VIEWTYPE menu.

Jerzy

Tomasz Sowinski14-Aug-01 9:56

14-Aug-01 9:56

The handle of the IDR_XXXTYPE menu is accessible through public data member of the CMultiDocTemplate class, it's called m_hMenuShared.

Tomasz Sowinski -- http://www.shooltz.com

JerzyPeter14-Aug-01 11:30

14-Aug-01 11:30

Hi Tomek,

Thanks for the solution. It works - it ataches a new popup to IDR_XXXTYPE menu.

But the problem is that I don't know where this code should be placed. If I put it in OnCrete() of ChildFrm, then the new popup is atached as many times as ChildFrm frames were created.

MSDN says something that this menu is loaded during the construction of the document templates. Can I override this?

Thanks for any suggestions.
Jerzy

Tomasz Sowinski16-Aug-01 0:54

16-Aug-01 0:54

You should add popups after creating new CMultiDocTempltate, in CYourApp::InitInstance.

Tomasz Sowinski -- http://www.shooltz.com

JerzyPeter16-Aug-01 9:28

Simple socket problem under WinCE

16-Aug-01 9:28

Hi Tomek,

Thank you very much for this tip. It works. I had to only call DrawMenuBar() to refresh the menu. Without this call the menu was updated only when the mouse was over the menu. (This is only when the application starts).

When all documents were closed and then I opened a new one the menu was shown correctly.

Dziekuje,

Jerzy
Smile | :)

14-Aug-01 6:17

Netmeisters,

I have a problem with what appears to be a very simple operation. I'd like to use sockets in a simple client application. Initially, to create and connect a socket, I did this:

CCeSocket mySock;
mySock.Create();
mySock.Connect(_T("dp1.derm.mcw.edu"),23501);

However, I'd now like to move to secure sockets, so I thought I'd use the socket handle rather than the socket class. So I changed to this:

SOCKET s;

s=socket(AF_INET, SOCK_STREAM, 0);
SOCKADDR_IN tcpaddr;
tcpaddr.sin_family=AF_INET;
tcpaddr.sin_port=htons(23501);
tcpaddr.sin_addr.s_addr=inet_addr
("dp1.derm.mcw.edu");
int res=connect(s, (SOCKADDR *)&tcpaddr, sizeof
(tcpaddr));
if (res==SOCKET_ERROR) {
CString err;
err.Format(_T("Error
d\n"),WSAGetLastError());
MessageBox(err);
}

This fails with an error 10049, "The requested address is not valid in its context".

I suppose I could use CCeSocket to create the socket and then get the socket handle from the class, but I am annoyed that this doesn't work. Why?

Thanks very much,

Matthew Fleming
mgf@mcw.edu

Help! My App crashes and I've no idea why!

14-Aug-01 6:16

Hi,

I've written an MFC MDI app, not using CDocument.

My View class is derived from CTreeView.

Whenever I close a view window, I get an error. When debugging the program and closing the view window, I get a dialog box "User breakpoint called from 0xXXXXXXX" where the 0xXXXXXX is some memory address. My program has no breakpoints, and the debugger stops in a dissasembly window with no relation to my code that i can see.

In the little information window at the bottom, the following line is present:

HEAP[j5manager.exe]: Invalid Address specified to RtlValidateHeap( 910000, 915314 )

My view class is pretty basic- it doesn't do much yet. Default constructor and destructor, they do nothing. The class has 4 member vars, Two CStrings, an HTREEITEM and a CPtrList, but I've not done anything with these so far.

I'm really stumped as to what is causing the problem. Does anyone have any ideas or reccommendations on how to proceed? I'd post some code but I don't know what part to post!

Your help much appreciated.

Thanks

Jon

Re: Help! My App crashes and I've no idea why!

Tomasz Sowinski14-Aug-01 7:35

Re: Help! My App crashes and I've no idea why!

14-Aug-01 7:35

Your heap gets corrupted. One of the reasons could be writing past the end of memory block allocated by new or malloc. Do you have any diagnostic tools, like BoundsChecker or Purify?

Tomasz Sowinski -- http://www.shooltz.com

14-Aug-01 22:03

sadly, no I haven't.

Not sure _how_ the heap could be corrupted? like i said, the view class does pretty much nothing at the moment.

CArchive, Serializing & Schema

Jason Teagle14-Aug-01 5:50

14-Aug-01 5:50

I have a situation where I need to serialize several parts of a document-derived class. Because the standard doc loading / saving mechanism is not quite what I need, I have to construct the CArchive manually. All the serialization is working fine in itself, but the one thing I can't seem to get to work now I need it is the schema business.

My doc-derived class uses IMPLEMENT_SERIAL() with the current schema number correctly. I create the archive correctly and then start serializing out (when saving, this is)... but for some reason it never saves the schema in the binary file. I tried SetObjectSchema() immediately after constructing the CArchive, which certainly sets the internal schema value... but that never gets written to file.

I looked at the code for CDocument where it calls our overriden Serialize() to see how it did it - from that I see it sets the archive's m_pDocument and another member. So I did this also... STILL doesn't save the schema in the file.

Since CDocument::Serialize() does not do anything, calling the base class has no effect.

Any clues as to what I'm missing? Otherwise I'll have to do the schema bit myself. But I'd rather use the built-in stuff as much as possible.

Tomasz Sowinski14-Aug-01 6:01

14-Aug-01 6:01

How are you serializing document members? Using m_foo.Serialize(ar) or ar << m_pFoo?

Tomasz Sowinski -- http://www.shooltz.com

Jason Teagle14-Aug-01 6:11

14-Aug-01 6:11

Everything is done using ar << m_pFoo (no objects other than CString are serilaized - most of what is saved is structures, and I do the members of each by hand).

You sound as if you're hinting that each object (class) has its own schema... which I can understand... but should there not be an overall schema for the document / doc-derived object? It does, after all, have IMPLEMENT_SERIAL()...

Basically, I'm not interested in the individual schemas of each thing I serialize - all serializing is done from one class (the doc-derived) (since there are no child objects being serialized, not even CXXXArrays). I want one overall schema that is used in all serializing operations so that I can check it on loading to avoid loading new data from old-schema files...

Jason Teagle14-Aug-01 6:12

14-Aug-01 6:12

Tomasz Sowinski14-Aug-01 6:27

14-Aug-01 6:27

Schema number is written to file only if you use CArchive::WriteObject (operator << for CObject pointers calls this method). WriteObject uses CArchive::WriteClass for sort of 'metadata' (class name, schema version).

Default serialization implemented in CDocument::OnSaveDocument uses plain Serialize. This means that you can't call GetObjectSchema to get document schema number in CYourDoc::Serialize - it's not in the file.

You've mentioned that you're creating CArchive yourself - if you're replacing OnSaveDocument you can also try to replace CYourDoc::Serialize() with ar << pDoc.

Tomasz Sowinski -- http://www.shooltz.com

Jason Teagle14-Aug-01 6:36