Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!cs.utexas.edu!yale!bunker!shap
From: shap@bunker.UUCP (Joseph D. Shapiro)
Newsgroups: comp.windows.ms
Subject: Usher menus are NOT slow.  (and a suggestion)
Message-ID: <17074@bunker.UUCP>
Date: 18 Jan 91 19:09:51 GMT
Reply-To: shap@clunker.UUCP (Joseph D. Shapiro)
Distribution: comp
Organization: ISC-Bunker Ramo, an Olivetti Company, Shelton, Ct
Lines: 28


I do not remember who started the discussion about the cascading menus
in Usher being slow, but they are not... Windows is introducing that
delay intentionally.

The confusion arises because Usher is a "HOLD DOWN THE LEFT BUTTON"
utility.  this causes people to continue to hold the button even after
the menu is selected.  In this case, windows WAITS about a second and
then draws the sub menu.  POWERPOINT displays this, as does the system
menu for the DOS box.  Experiment to see for yourself.  The fact that not
too many programs use the nested menu technique probably adds to the confusion.

If you highlight the menu and then LET GO the menu comes up right
away.

----

And now the suggestion, unrelated to menus -- the Run... dialogue box
will allow you to change the file spec from *.EXE to say, *.DOC.  Of
course, there is an association between .DOC files and WINWORD.EXE, but
if you RUN... x.doc, it generates an application error or an integrity
violation or some such.  How bout if you check the associations and
launch the application with the file name as an argument?
-- 
__--__--__--__--__--__--__--__--__--__--__--__--__--__--__--__--__--__--__--__
Joe Shapiro					"My other car is a turbo...
ISC-Bunker Ramo     				 ...too."
{decvax,yale,philabs,oliveb}!bunker!shap