Menu Editor
Menu Editor ....
Enter your menu names (what user sees in your application's menu) in the main window. One per line. Use '&' sign to design desired shortcuts as usual.
Blank lines are Menu Separators. Never enter any blank line if you do not expressly want a Separator between two items. No blank line as first or last line!
Use [tab]s to define your menu levels organization. In this new version, you no longer have to set the flags for Popup / Item / LastItem / LastPopup. The editor does it better than us, ... after analysis of tabs.
Use [tab] too, to separate menu item name from menu Items hotkeys. example: '&Paste[tab]Ctrl+V'. This will prevent the 'keys' to be part of the equate name you will be given back, for use in your message loop.
'ID_Menu' value is used to stand all the IDs numbers of a menu. Instead of writing, for as many items [M00_New 1001 M00_Open 1002 ....], you simply write one '1000' in this edit box and the editor does the job: When over, click on 'Equates > Clipboard', go to your source and paste (Ctrl/V) to get all the menu equates at once. Do this each time you modify your menu and avoid modifying the names once done, as you would have to modify your source evocations too... For namings, do not use signs that would conflict with RosAsm symbols writing convention (math signs, reserved signs).
Example of flags, as set by the Editor after 'tabs' analysis:
> File [* PopUp]
> &New [* Item]
> &Open [* Item]
> &Close [* Item]
> ; true separator
> E&xit [* LastItem]
> &Help [* LastPopUp] ; last popup of level 1
> &About [* Item]
> ; true separator
> Topics [* LastPopUp] ; last popup of 'Help level' (level 2)
> &Editor Help [* Item]
> &Criptor Help [* LastItem] ; closes the list
To edit the 'Grayed' flag, double-click on each menu item in order to make the CheckBox active. Menus data have several other flags to allow 'dead hot keys', 'checked Items' 'Radio items'. They are not yet implemented. (We usually prefer to set them at run time by Api calls anyway... more consistent).
~~~~~~~