Path: utzoo!attcan!uunet!zaphod.mps.ohio-state.edu!usc!cs.utexas.edu!ico!attc!marbru
From: marbru@attc.UUCP (Martin Brunecky)
Newsgroups: comp.windows.x.motif
Subject: Re: Tanslation tables problem.
Keywords: translation, action.
Message-ID: <921@attc.UUCP>
Date: 10 Dec 90 15:59:18 GMT
References: <1990Dec7.003012.4153@bellcore.bellcore.com> <4296@soleil-tx.oakhill.UUCP> <1990Dec7.151845@casee.enet.dec.com>
Reply-To: marbru@auto-trol.UUCP (Martin Brunecky)
Organization: Auto-trol Technology, Denver
Lines: 32

In article <1990Dec7.151845@casee.enet.dec.com> lalli@casee.enet.dec.com () writes:
>is
>|>>acting like #replace.  I have also tried, #replace, and #override, they all
>act
>|>>like #replace.
>|>
>|>This is a bug in Motif 1.0.  I don't know if it is fixed in 1.1.
>|>
>
>I experienced the same problem augmenting a PushButton translation table, 
>using both Motif 1.0 and Motif 1.1. So I don't think it's been fixed yet.
>
   I'd call it a "feature".
   Motif has rather "inovative" approach to translation tables. By default,
   the table is NULL.
   If there is nothing specified (either in resource file, or in args), the
   widget's Initialize finds: Oh, there is NULL in translations, lets use
   our default ones.
   If, however, the translatins have become non-NULL, the default translations
   are NOT used at all. Thus, using #augment, #override or a new table has
   identical effect: defines the new translations. The only way you can
   (I *think*) augment/override Motif's default translations is AFTER
   Initialize, using SetValues.
   Note, however, that Motif managers do play with translation tables as
   well ... so that results are not always easy to predict.


-- 
=*= Opinions presented here are solely of my own and not those of Auto-trol =*=
Martin Brunecky                           {...}sunpeaks!auto-trol!marbru
(303) 252-2499                        (sometimes also:  marbru@auto-trol.COM )
Auto-trol Technology Corp. 12500 North Washington St., Denver, CO 80241-2404