Path: utzoo!yunexus!ists!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!samsung!usc!apple!sun-barr!decwrl!asente
From: asente@decwrl.dec.com (Paul Asente)
Newsgroups: comp.windows.x
Subject: Re: Another Resource file question
Message-ID: <2123@bacchus.dec.com>
Date: 17 Nov 89 20:24:20 GMT
Article-I.D.: bacchus.2123
References: <1989Nov17.023437.9716@agate.berkeley.edu> <8911171804.AA12209@expo.lcs.mit.edu>
Organization: DEC Western Software Lab
Lines: 31

In article <8911171804.AA12209@expo.lcs.mit.edu> converse@EXPO.LCS.MIT.EDU (Donna Converse) writes:
>The resource database entry might look
>look something like this:
>
>Xmh*someWidgetName.Accelerators: #override\n\
>         Meta<Key>space: XmhViewNextMessage()\n\
>        :Meta<Key>c:    XmhMarkCopy()\n\
>        :Meta<Key>d:    XmhMarkDelete()\n\
>        :Meta<Key>f:    XmhForward()\n\
>        :Meta<Key>m:    XmhMarkMove()\n\
>        :Meta<Key>n:    XmhViewNextMessage()\n\
>        :Meta<Key>p:    XmhViewPreviousMessage()\n\
>        :Meta<Key>r:    XmhReply()\n\
>        :Meta<Key>u:    XmhUnmark()\n

Er, no.  The accelerators should be defined upon the widget that exports
the accelerated function, not the one that installs it.  So your database
would look something like

Xmh*nextButton.Accelerators: #override\n\
         Meta<Key>space: Notify()
Xmh*copyButton.Accelerators: #override\n\
        :Meta<Key>c:     Notify()
Xmh*deleteButton.Accelerators: #override\n\
        :Meta<Key>d:     Notify()

and so forth.  There's still the problem that xmh doesn't install
the accelerators for you.

	-paul asente
	    asente@decwrl.dec.com	decwrl!asente