NetNews Usenet Archive 1992 #16/NN_1992_16.iso/spool/comp/sys/mac/programm/12976

Internet Message Format | 1992-07-23 | 1.9 KB

Path: sparky!uunet!zaphod.mps.ohio-state.edu!wupost!waikato.ac.nz!ldo
From: [e-mail] (Lawrence D'Oliveiro, Waikato University)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Things That May Become Dim
Message-ID: <[e-mail]>
Date: 24 Jul 92 18:32:50 +1200
References: <[e-mail]> <[e-mail]>
Organization: University of Waikato, Hamilton, New Zealand
Lines: 23

In article <[e-mail]>, [e-mail] (JohnC) writes:
> In article <[e-mail]> [e-mail] (P. Hawthorne) writes:
>>If a non-movable modal dialog is up, should all of the menu titles on the
>>menu bar be dimmed, since you can't use them? What if one of the menus is
>>hilited to begin with, such as the Apple menu after bringing up an about
>>window that goes away as soon as you click?
>
> The guidelines say that menus and menu items that aren't available should be
> dimmed.  Before System 7, you couldn't click anywhere outside a modal dialog
> box, so it made sense to disable the entire menu bar.  Since System 7, Apple
> recommends that the Apple, Edit and other system menus remain available during
> modal dialogs.  I think the system handles this auto-magically for most cases.

I think the automagic only works if you use ModalDialog. I know I wrote some
code using IsDialogEvent/DialogSelect (because it was more convenient), and
I wasn't getting the special handling of the Edit menu; I changed the code
to call ModalDialog, and recoded my special item handling as a filter routine,
and cut/copy/paste then worked in my dialog.

Lawrence D'Oliveiro                       fone: [phone]
Computer Services Dept                     fax: [phone]
University of Waikato            electric mail: [e-mail]
Hamilton, New Zealand    37^ 47' 26" S, 175^ 19' 7" E, GMT+12:00