Explanation of menu merging

[Dave Taylor]

Is there a decent explanation of how menu merging with MDI forms work in
VB.NET? I've read through the online help and it still seems that whenever
I change menus around or whatever, it breaks everything. VB6, as repetitive
as it was to retype menus, was at least consistent. It seems that VB.NET
throws menu items wherever it feels like.

 

[Herfried K. Wagner [MVP]]

Is there a decent explanation of how menu merging with MDI forms work in
VB.NET? I've read through the online help and it still seems that whenever
I change menus around or whatever, it breaks everything. VB6, as repetitive
as it was to retype menus, was at least consistent. It seems that VB.NET
throws menu items wherever it feels like.

Please be more specific. What exactly do you want to archieve and
what's the "problem" with doing that?

 

[Dave Taylor]

Herfried...

For example, I have the typical File, View, Tools and Help menus on my main
MDI form, all set to MergeItems, the subitems on those menus are set to Add.

On a child form I have File, Edit, View, Tools with some subitems.

When the menus merge, the Help menu completely disappeared, and some of its
items move to the File menu.

Finally, I have gotten this behaviour to stop by numbering (MergeOrder) the
MDI parent menus File (1), View (2), Tools (3), Help (4).

But this begs the question what about the Edit menu (in this scheme it would
be MergeOrder 1.5)....does this mean I should be numbering the items 10, 20,
30, 40 to leave enough space between items to insert additional items? What
I'm looking for is really a good explanation of how menu merging
works...Microsoft's documentation in this area is lousy IMO (and that of
others based on my Google searches about menu merging). A good book
recommendation would be great....I currently have VB.NET Programmer's
Cookbook and it doesnt even touch the subject.

Thanks

Dave Taylor