>On Tue, 28 Dec 1999, David Cramer wrote:
>
>> After a fairly hectic Christmas, I am going to be returning to work
>> on the following challenge tomorrow. So far, I have not received any
>> responses that get to the heart of the basic question "What
>> messages/properties can be referenced during the MetaCard stack menu
>> process?"
>
>I think the fundamental problem here is that the behavior you desire,
>clicking on the menu button to close an open menu panel, isn't built
>in. Any script-based workaround for this "problem" would be
>complicated, unstable, and likely to break when the feature gets
>implemented in the future. So your best bet is just to wait. If it's
>any consolation, no one has reported this as a problem before (or
>*still*, according to our bug list), a fact that I would consider
>significant since most look and feel deviations result in multiple bug
>reports. I myself wasn't aware of this "feature" and I'd be willing
>to bet that 99% of Windows and MacOS users aren't either. Clicking
>any place other than on that button does close the menu, which is the
>usual way people close menus they don't want.
> Regards,
> Scott
>
Actually this is typical behavior on MacOS and I think it came into being
at the same time with menus that stay open without having to keep the mouse
down. MC's current menu-button behavior implies that one doesn't open a
menu without selecting a menu item which is 80% true at least in my case.
MC menus under MacOS inherit the system's behavior so it's hard to detect
the problem unless you use a menu-button in a stack.
For Windows I guess, if one could fake more "ilegal operations", should do
for look and *feel* even without the proper menu behavior ;-)
Regrds, Andu
This is the MetaCard mailing list.
Archives: http://www.mail-archive.com/metacard%40lists.best.com/
Info: http://www.xworlds.com/metacard/mailinglist.htm
