commandKeyDown
Richard Gaskin
ambassador at fourthworld.com
Thu May 6 16:49:58 EDT 2004
Robert Brenstein wrote:
>>
>> This will cause problems with any menu in your own stack that uses
>> Cmd-1 through 4.
>>
>> I propose removing those but keeping the optionKey section for script
>> access:
>>
>> Are more people relying on maintenance of this behavior than are
>> adversely affected by it?
>
> Actually, I do rely on cmd-number to navigate stacks in development
> mode. In this mode, MC shows its default menubar not the one from our
> programs, so no conflict is possible. Therefore, I believe a better
> approach would be to check the defaultmenubar setting and execute
> cmd-number when it is the default and pass commandKeyDown otherwise.
I agree that checking makes the most sense, but the defaultMenuBar is
not necessarily the active one, as any window with a menubar will have
its menubar active when it is in front.
Is there a robust way to check for the current menubar?
--
Richard Gaskin
Fourth World Media Corporation
___________________________________________________
Rev tools and more: http://www.fourthworld.com/rev
More information about the metacard
mailing list