Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!Eng.Sun.COM!argv
From: argv@Eng.Sun.COM (Dan Heller)
Newsgroups: comp.windows.x.motif
Subject: Re: Motif Translations
Message-ID: <9009200100.AA10011@turnpike.Eng.Sun.COM>
Date: 20 Sep 90 01:00:35 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: <argv@Sun.COM>
Distribution: inet
Organization: The Internet
Lines: 24

On Sep 19,  4:45pm, Mitch Kuninsky (x2677) wrote:
> Dan Heller writes:
> > Let the application specify and provide whatever alternatives
> > it thinks is reasonable and act as the mediator between the
> > user and the toolkit.
> Yes, and one way to do this is through the resources in
> the application's app-defaults file.
...
> All I wanted to do was augment the translation table of all my widgets
> with the following:
>     <Key>Help:	Help()

I know this is a problem.  I have been pulling my hair out about it
myself!  I don't disagree that there are definitely problems with
the Motif toolkit in this regard.  However, please don't misunderstand
my point, which was a general one -- there is nothing "wrong" with
making specifications for an arbitrary UI toolkit and making restrictions
in the toolkit to provide for those specs.

In this case (and many others, I might add), the Motif toolkit makes
some errors that are quite distressing.


--dan