Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!columbia!cunixc!cunixf!marg
From: marg@cunixf.cc.columbia.edu (Margarita Suarez)
Newsgroups: comp.windows.x
Subject: help with athena widgets
Message-ID: <1989Dec13.165245.9710@cunixf.cc.columbia.edu>
Date: 13 Dec 89 16:52:45 GMT
Reply-To: marg@cunixf.cc.columbia.edu (Margarita Suarez)
Distribution: usa
Organization: Columbia University
Lines: 29

i'm preparing a final project for a user interfaces class, and i'm
running into a few obstacles using athena widgets (nah, you don't say?).
here are a few questions i hope someone can answer...

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?

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.

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.  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.  problem is
    that all the routines defined in Text.c and TextTr.c are declared
    static, so i can't call them myself.  any ideas?

i thank you all for your several prompt and enlightening responses.  :-)

marg

 VOICE:  w:212-854-5434 h:212-932-3023 | The important thing about a battleship
INTERNET:  marg@cunixc.cc.columbia.edu | is that it shoots.  It floats, and it
 BITNET:            marg@cunixc.bitnet | is a ship, but the important thing
  UUCP:  !rutgers!columbia!cunixc!marg | about a battle ship is that it shoots.