Event Handler Wizard

[Cliff Hatch]

I never had any problems creating and finding event handlers using the C++ V6.0 ClassWizard but I don't find C# so easy to use in this respect. I have resorted to editing the code without the aid of a wizard on many occasions but I'm sure this can't be the best way - I imagine I'm missing something obvious:confused:. I have two specific questions: How do you add an event handler to a Toolbar button? Double clicking doesn't do anything, if you right click there is no "add event handler" option, and the Control Events button does not appear on the Properties view. All these things work with Dialog buttons, why not with Toolbar buttons? How do you create and locate handlers for UPDATE COMMAND UI messages? The V6.0 ClassWizard used to show these clearly but I can't find any reference to them on the C# Event Handler Wizard or the Properties view. Any assistance would be greatly appreciated. Best Regards Cliff Hatch

[mav northwind]

Cliff, .NET is a bit different than MFC. By doubleclicking a control in the visual designer you'll get an event handler created for the control's default event. If you want to add any other eventhandler visually, then you'll have to use the Control Events button to show the events a selected control supplies (and which are marked designer-visible). Nevertheless, adding event handlers manually is just as easy. For example, adding a click event handler to a button in VS.NET can be achieved by typing myButton.Click += and then TAB twice. VS.NET finishes the statement and adds a new myButton_Click() event handler with the correct signature. If the Control Events button doesn't appear for a certain control then this control doesn't have any public visible events. Regarding the click on a ToolButton, this event is fired by the ToolBar containing the button. And for menus, there's the Popup event that's fired just when a menu is about to appear, so you can use this event to enable/disable your menu items. Regards, mav

[Cliff Hatch]

mav Thankyou for your clear reply. I now understand why the system behaves as it does, and I will try your method of adding handlers manually. I'm still puzzled why the designers of .NET chose this route though. I wonder if they planned to discard MFC's wizard support for the creation of ToolButton and Update handlers, or if this was an unintended side effect of design rationalisation. Best Regards Cliff

[Cliff Hatch]

After a bit more exploration I found that I had indeed missed something: If you right click on menu items and select the "add event handler" option, the Event Handler Wizard appears and gives you the option to create or edit COMMAND and UPDATE_COMMAND_UI messages - so that's where they're hidden! The rule seems to be: right click on the thing you want to create a handler for and the Event Handler Wizard will provide pretty much the same functionality as MFC's ClassWizard - except that it doesn't work for toolbar buttons because you don't get an opportunity to call it up. I suppose one way round this is always to build a menu item first, attach handlers to it, then build a toolbar button with the same ID - and it will share the same handlers. Perhaps it is good practice to replicate every toolbar function in a menu, so maybe this approach makes sense. On the other hand, I don't see why a right click on the toolbar shouldn't offer the "add event handler" option. The treatment of toolbar buttons seems inconsistent with that of menu items and dialog buttons. Best Regards Cliff