Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!bloom-beacon!EXPO.LCS.MIT.EDU!kit
From: kit@EXPO.LCS.MIT.EDU (Chris D. Peterson)
Newsgroups: comp.windows.x
Subject: Re: help with athena widgets
Message-ID: <8912132030.AA09046@expo.lcs.mit.edu>
Date: 13 Dec 89 20:30:44 GMT
References: <1989Dec13.165245.9710@cunixf.cc.columbia.edu>
Sender: root@athena.mit.edu (Wizard A. Root)
Organization: The Internet
Lines: 56


> 1)  how do i get awm not to decorate the windows in my application?
>    what resources must be referenced/defined and how do i do it?

I believe that the awm man page explains how to turn off decorations on certain
the windows if a given appliacation.  This is specifiable by the user of awm,
not the application programmer.

> 2)  how can i define the geometries of application shell windows besides
>     doing it in .Xresources?  i will be creating several "parent" shells and
>     i want the windows to come up in predetermined locations on the
>     screen.

Using TransientShellWidgetClass will usually place the window where the
application specifies in the XtNx and XtNy resources, w/o a geometry
specification (the exact semantics are left up to the window manager).  It may
also cause the window manager not to decorate the window (again this is left up
to the specific window manager).

> 3)  how do i *add* a routine to the default event translations for a
>     widget? i would like to have the event manager call my own routine in
>     addition to the default routine, but if i use XtAugmentTranslations, the
>     event manager ignores duplicate events.

Really?? I think that Augment should do the right thing.

>   for example, i would like
>   to have <Btn1Dn> in a text widget call my routine HighlightLabel and
>   also call the default routine for this event, SelectStart.

In order to make sure you get the order right I would suggest using something
like this:

{
	static char trans[] = "<Btn1Down>:     HighlightLabel() select-start()";

	XtOverrideTranslations(widget, XtParseTranslationTable(trans));
}

You will need to register your action with XtAppAddActions(), of course.
This will guarantee that your action will be called before select-start().

>    problem is
>    that all the routines defined in Text.c and TextTr.c are declared
>    static, so i can't call them myself.

This is not a problem, but a feature, the implementation of these routines is 
internal to the Text widget (and may change w/o notice).


						Chris D. Peterson     
						MIT X Consortium 

Net:	 kit@expo.lcs.mit.edu
Phone:   (617) 253 - 9608	
Address: MIT - Room NE43-213