Oh yes, nested submenus are quite easy. below is an example of a menu of mine, which has sever items in a submenu; the basic idea is that you begin the sub menu with the menu declaration tag <menu ...>, then the text of the menu name, then instead of following up with the closing </menu> tag, you begin defining all the items which are choices in your submenu:
<menu id="script_options_alerts_POI" shortcut="p"> Points of Interest <menuItem id="script_POI_announce" shortcut="a" >Announce POIs</menuItem> <separator/> <menuItem id="script_POI_play_sound" shortcut="p" >Play a Sound for POIs instead of Speech</menuItem> <menuItem id="script_POI_use_mappoint" shortcut="m" >Use POIs From MapPoint</menuItem> <menuItem id="script_POI_use_other" shortcut="o" >Use Other POIs</menuItem> <separator/> <menuItem id="script_POI_choose" shortcut="c" >Choose POI Categories to be Used</menuItem> </menu> <!-- POI --> When you go to find out which item was selected in your handler, you treat them all as if they were at the top level; you do nothing special because the items were down in a submenu, and just test for their item id's, like you would any other top level menu item. hth, Chip -----Original Message----- From: Kevin Huber [mailto:[email protected]] Sent: Thursday, November 11, 2010 11:09 AM To: [email protected] Subject: Re: Proofreading script on Sendspace Hi J.J.: That sounds like a good idea. I will just have to figure out how to do it, but it does sound like a good idea. I was also wondering about nested submenus. Is it possible to have nested submenus? Kevin Huber On 11/10/10, J.J. Meddaugh <[email protected]> wrote: > Kevin, > What if you added a dialog box with checkboxes for the various > options? Then after they pressed OK on the box, you would just need to > check the state of the checkboxes and apply the necessary changes. > You could link to this dialog box from the script menus. > > > J.J> Meddaugh - ATGuys.com > Your Assistive Technology Experts > ----- Original Message ----- > From: "Kevin Huber" <[email protected]> > To: "gw-scripting" <[email protected]> > Sent: Wednesday, November 10, 2010 5:00 PM > Subject: Re: Proofreading script on Sendspace > > >> Hi Steven: >> I think the help dialog will only allow you to change the hotkeys, >> rather than to activate them. I want to activate the hotkeys and >> stay in the menu, if that is possible. >> For example, when I want to turn Say Attributes On, I want to go into >> that item in the Proofreading Submenu and press Enter rather than >> pressing the hotkey shift-alt-a. I want to add this feature for >> those people who can't, or do not wish to, remember hotkeys. >> Kevin Huber >> >> On 11/10/10, Stephen Clower <[email protected]> wrote: >>> Kevin, >>> >>> Why not link to your script's help from the menu and use the hotkey >>> manager in the standard help dialog? What you propose with the menus >>> is highly unusual. >>> >>> Regards, >>> Steve >>> >>> >>> >>> >>> On 11/10/2010 4:11 PM, Kevin Huber wrote: >>>> Hi: >>>> I have put a revised version of my Proofreading script on Sendspace >>>> and a link to download it has been sent to the list. >>>> I have put all the hotkeys except for shift-alt-h for the list of >>>> hotkeys and shift-alt-s to save the settings, in a submenu in the >>>> Script Menus pulldown menu in the Window-eyes control panel. >>>> As you will see, if you press Enter on any of the items in the >>>> Proofreading submenu, save for Script Help, you are taken out of >>>> the submenu and left in the Window-eyes Control Panel. >>>> I think it would be better if it stayed in the Proofreading >>>> submenu, but I don't know how to accomplish this. I would welcome >>>> any suggestions on how to do this or any other suggestions on what >>>> I could do to improve this script. >>>> Thank you very much in advance. >>>> Kevin Huber >>> >>> -- >>> Stephen Clower >>> Product support specialist >>> GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825 >>> 260-489-3671 * gwmicro.com >>> >> > >
