Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!sdd.hp.com!hp-pcd!hpcvlx!gabe
From: gabe@hpcvlx.cv.hp.com (Gabe Begeddov)
Newsgroups: comp.windows.x.motif
Subject: Re: XmPushButton translations
Message-ID: <110630005@hpcvlx.cv.hp.com>
Date: 25 Jul 90 00:34:20 GMT
References: <4bc78cb1.20b6d@apollo.HP.COM>
Organization: Hewlett-Packard Co., Corvallis, OR, USA
Lines: 37


   / hpcvlx:comp.windows.x.motif / daniel@osf (Daniel Dardailler) /  6:24 am  Jul 24, 1990 /
   From article <4bc78cb1.20b6d@apollo.HP.COM>, by aw@cellar.bae.bellcore.com (Andrew Wason):
   > 
   > [Sparc 1+, SunOS 4.1, ICS Motif 1.0, X11R4 server]
   > 
   > I'm having trouble specifying translations for the XmPushButton widget.
   > If I specify them as #augment or #override, they instead seem to #replace
   > the PushButtons default translations.  Here's a simple example
   > ...
   > Has anyone else seen this or am I doing something wrong?
   
   
   This was a bug, it's fixed in 1.1.
   
It's not a bug, it's a feature :-). Unfortunately, I think this feature is 
still in 1.1. The problem is that the PushButton is schizophrenic. It has
a different translation personality depending on it's context (whether it's
in a pulldown or popup menu or not). This information can only be 
ascertained in the initialize routine (as currently structured) and is 
unavailable at the time that the resource list is processed. What motif 
does is to leave the translations null and set them in the initialize 
routine. If the translations have been set by the client and/or user then
the code assumes that a complete table will be provided. 

           Daniel Dardailler          |          OSF/Motif Team  
        Open Software Foundation      |      Email : daniel@osf.org           
          11 Cambridge Center         |      Phone : (617) 621 8840    
          CAMBRIDGE, MA 02142         |      Fax   : (617) 621 0584
   ----------
   
Gabe Beged-Dov   
HP Interface Technology Operation
Corvallis, Oregon