CompuServe Thread

#WSHELL 2.0 menu probs

4 messages in this thread
#18343From: larry julienDec 27, 1991 12:19 AM
I'am having problems getting a menu to appear. The following is in my User-Startup-DHOpts PIP: CNC:0/11/640/200/NEW/CLOSE MENU S:cnc-menus Assign dismount CON: DHOpts CON:0/11/640/200/Displayhandler!/CLOSE MENU S:cnc-menus I have yet to see a menu! Maybe someone can help??
#18344From: John DraperDec 27, 1991 12:31 AM
Sorry, but I have never tried menus with WShell 2.0, so I have no idea what the problem might be.
#18354From: Jim Nangano/SYSOPDec 27, 1991 10:01 AM
I _have_ managed to get the menus to work. My DHOpts arguments are similar to yours and I see nothing wrong offhand (other than the CIS formatting snafu). The one additional piece that I needed to use was to specify the MENU keyword in my actual "CON:" window specification when the window was opened. Basically, I have the following in the Environment Variable "shellwindow": CON:0/0/714/478/ShellWindow/C/menu cnc-menus and now I do have the menus attached to my console window. Hope this helps…. …BobR
#18368From: tom millerDec 27, 1991 6:25 PM
Bob Rakosky is correct about the ENV:"shellwindow", but this will give you the _same_ menu with every shell you open. You can open a different menu with each shell you use! Each menu must be defined with "DHOpts MENU menu_name" and then opened with a call like: Wshell Con:/Menu#CNC-Menus OR Wshell Con:/Menu#MyMenu Both these shells will have different menus. The MENU keyword is an option to both the DHopts and the CON: command. P.S. You are defining two consoles in your startup a CNC: and a CON: Are you using both or was that a mistake? I like the CON: and if thats what you like use the Assign dismount CON: followed by the DHopts. I'd add the PIP: attrabute to the CON: line.