+ the radio items risks to not work correctly.
+
+
+ @section menu_allocation Allocation strategy
+
+ All menus must be created on the @b heap because all menus attached to a
+ menubar or to another menu will be deleted by their parent when it is
+ deleted. The only exception to this rule are the popup menus (i.e. menus
+ used with wxWindow::PopupMenu()) as wxWidgets does not destroy them to
+ allow reusing the same menu more than once. But the exception applies only
+ to the menus themselves and not to any submenus of popup menus which are
+ still destroyed by wxWidgets as usual and so must be heap-allocated.
+
+ As the frame menubar is deleted by the frame itself, it means that normally
+ all menus used are deleted automatically.
+
+
+ @section menu_eventhandling Event handling
+
+ If the menu is part of a menubar, then wxMenuBar event processing is used.
+
+ With a popup menu (see wxWindow::PopupMenu), there is a variety of ways to
+ handle a menu selection event (@c wxEVT_COMMAND_MENU_SELECTED):
+ - Provide @c EVT_MENU handlers in the window which pops up the menu, or in an
+ ancestor of that window (the simplest method);
+ - Derive a new class from wxMenu and define event table entries using the @c EVT_MENU macro;
+ - Set a new event handler for wxMenu, through wxEvtHandler::SetNextHandler,
+ specifying an object whose class has @c EVT_MENU entries;
+
+ Note that instead of static @c EVT_MENU macros you can also use dynamic
+ connection; see @ref overview_events_bind.