Printable View
In my MDI application,I want the main menu bar not to be replaced with the child menubar.When a child frame is opened from the mainmenu item, the additional menu items from the childmenu bar to be shifted to the main menu bar. Is it possible? If yes, Please Help
regards
Change your MDI application into an SDI application having several child windows. This will be easier than to customize MDI menus.
Already 90% of my project is complete,so please help
regards
What's the point in doing it that way?Quote:
Originally Posted by Plaban
Of course it is posiible!Quote:
Originally Posted by Plaban
But it cannon be done "magically". You will have to write code to do it:
get old menuAnd this process you will need to run every time you activate another document or frame.
remove all items you don't need
load new (child frame) menu
enum its subitem, get subitem data and move to the "old" menu
destroy the old menu
set a new cretated/updated menu
redraw rhe menu bar
So the main question is: why not to let the Framework replace your menus? :confused:
In the call to my child frame handler function, if I set to the main menu, it works but the problem is that after opening to the multiple child window,if I switch to any window,from the opened windows,then the main menu bar gets replaced with the child menu bar. Where should I set the menu,so that the main menu doesn't gets replaced even when switching to different open windows .
regards
Does CDocument::GetDefaultMenu() is a member function of CDocument?If yes,how to access it.
regards
It is written in the tutorial about CMDIChildWnd::m_hMenuShared Data member,but I am not getting data member for this class or any other base classes. Please help
regards
Define "am not getting data member".Quote:
Originally Posted by Plaban
Have you tried to just copy/paste the code from "How to Use Multiple Menus in MFC App That Uses GetDefaultMenu" article? Doesn't it complile? Doesn't it work?
And BTW, the code sample from "INFO: Sharing Menus Between MDI Child Windows" allow you to use the same menu for all your documents! It is exactly what you asked:Quote:
Originally Posted by Plaban
Yes, "Sharing Menus Between MDI Child Windows" is the answer to my Question. But the problem is that my Menu bar contains Navigational menu items and if I open multiple MDI child windows,after closing the last opened window, the Navigational menu items of the present active window does not works. And one more question few data members as m_hMenuShared of class CMultiDocTemplate given in the "Sharing Menus Between MDI Child Windows" is not present, but still it works after I wrote the code.Why and how to get these members?
regards
What is "Navigational menu items"?
:confused:Quote:
Originally Posted by Plaban
If "it works" then all these data members are present. However, some of them might be undocumented, therefore not visibile in the intellisense...
Navigational menu items means like moving to next record with the help of CRecordSet::MoveNext ,CRecordSet::MoveFirst... These menu items does not works.Quote:
Originally Posted by VictorN
regards
In what class do you handle CRecordSet::MoveNext ,CRecordSet::MoveFirst... actions?
In their CRecordView derived classes of the respective views.Quote:
Originally Posted by VictorN
These items can work only whe one of these "CRecordView derived classes" is active.
On closing one of the window the next below window becomes Active. How can I accomplish this, so that the shared menu bar's navigational items works for all the shared opened windows.Quote:
Originally Posted by VictorN
regards
You could move these message handlers to the Document class (or classes if you have more then one CDocument derived class, however it would be not always a good idea)
Sorry, I have not given any message handler for the Navigational menu items.I have only specified the message Id i.e ID_RECORD_NEXT,etc. It worked when I did not used shared menu, but now its not woking with shared menu.
regards
Then don't use shared menu. :cool:Quote:
Originally Posted by Plaban
Ann sorry, without knowing the architecture of your App it is impossible to say you more.