Click here to Skip to main content
15,888,984 members
Articles / Programming Languages / C#
Article

Magic MenuControl - VS.NET Style

Rate me:
Please Sign up or sign in to vote.
4.83/5 (45 votes)
29 Sep 20022 min read 338.3K   1.7K   101   60
Menus that mimic VS.NET/OfficeXP

Sample Image - MagicMenuControl.gif

Why another MenuControl?

The .NET Framework contains a wide range of user interface controls, but they offer only a basic look and feel. Today's user expects a richer experience that you just cannot build with the out-of-the-box controls. The Magic Library (of which this MenuControl is a major part) aims to solve this by providing a set of user interface elements that add the sophistication expected from modern Windows applications.

Downloads

The first download MenuControl Sample contains a example application that uses shows the MenuControl from the Magic Library. This allows you to experiment and test out the feature. The actual source code is inside the separate second download. At nearly 1MB in size, I thought people would prefer to download the sample before deciding if they want to install the entire source code project!

Description

The usual way to create a menu for your application is via the Menu property of your applications main Form. Unfortunately this gives a very basic look and feel and does not support the new Visual Studio .NET appearance.

This is where the MenuControl class comes into its own as it closely mimics the Visual Studio .NET look and feel. Not only that, but you can create as many instances as you like and place them anywhere on your Form. You can even use the Dock property to place the control against the left/right and bottom edges as well as the traditional top position. When placed on the left or right edges it will draw the menu items vertically.

When using the control within an MDI application it is important that exactly one instance of the MenuControl uses the MdiContainer property. This property should be given a reference to the MDI parent Form so that it can correctly display the pendant for MDI child Forms .

MenuCommand Instances

The control exposes a property called MenuCommands that contains the collection of MenuCommand instances for display. You cannot use the builtin menu designer to generate the instances and so will need to use code to create the structure you need. Look at the sample code to see how this is done.

PopupMenu

Also demonstrated in the sample is use of the PopupMenu class that can be seen by right clicking the RichTextBox present inside each MDI child instance. This shows how to create a context menu using the VS.NET/OfficeXP look and feel. It uses the same MenuCommand instances as the MenuControl.

More Details

Download and install the Magic Libary where a couple of more detailed artiles describe how all the various features of the MenuControl and PopupMenu work.

Revision History

30 Sept 2002 - Initial Revision

License

This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.

A list of licenses authors might use can be found here


Written By
Web Developer
United Kingdom United Kingdom
I am a big fan of .NET and have been working on developing a free user interface library to enhance the very basic controls that come out-of-the-box. Download the free source code project from http://www.dotnetmagic.com. I often carry out bespoke development work for companies, so feel free to email me for a quote on your .NET needs!



Comments and Discussions

 
GeneralFlickering with the top-level items Pin
TigerNinja_3-Oct-02 16:21
TigerNinja_3-Oct-02 16:21 
GeneralRe: Flickering with the top-level items Pin
Phil Wright3-Oct-02 22:37
Phil Wright3-Oct-02 22:37 
GeneralRe: Flickering with the top-level items Pin
Thong Nguyen27-Jan-03 16:59
Thong Nguyen27-Jan-03 16:59 
GeneralRe: Fix Pin
Thong Nguyen27-Jan-03 17:05
Thong Nguyen27-Jan-03 17:05 
GeneralSome minor issues Pin
Anonymous30-Sep-02 13:38
Anonymous30-Sep-02 13:38 
GeneralRe: Some minor issues Pin
Phil Wright30-Sep-02 22:02
Phil Wright30-Sep-02 22:02 
GeneralRe: Some minor issues Pin
Anonymous1-Oct-02 14:10
Anonymous1-Oct-02 14:10 
GeneralRe: Some minor issues Pin
Phil Wright1-Oct-02 21:54
Phil Wright1-Oct-02 21:54 
When I first wrote the class I assumed that it should appear in the component tray so that people could change the individual command properties quickly and easily. In practice, any real world application ends up with oodles of them which just starts to clutter the tray.

I have not changed it because I think it prevents the code persistence of collections from working correctly. Because it is a 'Component' it gets persisted via the usual method. If it does not derive from component then it gets persisted as binary and placed in the .resx file. At least I think thats the way it works.

Unless someone knows different?

Phil Wright
phil.wright@dotnetmagic.com
GeneralRe: Some minor issues Pin
lhrasko20-Jan-03 15:19
lhrasko20-Jan-03 15:19 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.