By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
446,205 Members | 1,027 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 446,205 IT Pros & Developers. It's quick & easy.

Problems with Visual Inheritance & Menus

P: n/a
I have created an MDI child form that I am using as a base form in a VB.Net
MDI application. The base MDI child form has a series of menu options on
it. I then use this form to create other MDI child forms (using
inheritance). The problem is that the derived MDI child form's menu options
don't seem to have inherited the functionality from the base form (i.e. the
inherited menu options don't work).

If I place a command button or other control on the base form the
functionality from the base form is available on the inherited forms. Does
anyone know what might be wrong? Is there a known bug regarding MDI forms,
menus, and visual inheritance? Any help will be greatly appreciated.

Matt
Jul 17 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Some additional information:
I am using Visual Studio.Net 2003 and the current installed .Net
framework is 1.1.

"Matt" <ma**@majecsoftware.com> wrote in message
news:aKyUc.7294$ni.4793@okepread01...
I have created an MDI child form that I am using as a base form in a VB.Net MDI application. The base MDI child form has a series of menu options on
it. I then use this form to create other MDI child forms (using
inheritance). The problem is that the derived MDI child form's menu options don't seem to have inherited the functionality from the base form (i.e. the inherited menu options don't work).

If I place a command button or other control on the base form the
functionality from the base form is available on the inherited forms. Does anyone know what might be wrong? Is there a known bug regarding MDI forms, menus, and visual inheritance? Any help will be greatly appreciated.

Matt

Jul 17 '05 #2

P: n/a
This group is pretty well dedicated to classic VB. There are .net-specific
groups on the msnews server ... try

news://msnews.microsoft.com/microsof...dotnet.general
news://msnews.microsoft.com/microsof...t.languages.vb
news://msnews.microsoft.com/microsof....vsnet.general

--

Randy Birch
MVP Visual Basic
http://vbnet.mvps.org/
Please respond only to the newsgroups so all can benefit.
"Matt" <ma**@majecsoftware.com> wrote in message
news:EMyUc.7295$ni.4167@okepread01...
: Some additional information:
: I am using Visual Studio.Net 2003 and the current installed .Net
: framework is 1.1.
:
: "Matt" <ma**@majecsoftware.com> wrote in message
: news:aKyUc.7294$ni.4793@okepread01...
: > I have created an MDI child form that I am using as a base form in a
: VB.Net
: > MDI application. The base MDI child form has a series of menu options
on
: > it. I then use this form to create other MDI child forms (using
: > inheritance). The problem is that the derived MDI child form's menu
: options
: > don't seem to have inherited the functionality from the base form (i.e.
: the
: > inherited menu options don't work).
: >
: > If I place a command button or other control on the base form the
: > functionality from the base form is available on the inherited forms.
: Does
: > anyone know what might be wrong? Is there a known bug regarding MDI
: forms,
: > menus, and visual inheritance? Any help will be greatly appreciated.
: >
: > Matt
: >
: >
:
:

Jul 17 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.