Path: utzoo!attcan!uunet!snorkelwacker!bloom-beacon!PIT-MANAGER.MIT.EDU!jik
From: jik@PIT-MANAGER.MIT.EDU (Jonathan I. Kamens)
Newsgroups: comp.windows.x
Subject: Which shell type should I use?
Message-ID: <8910262037.AA28434@pit-manager.MIT.EDU>
Date: 26 Oct 89 20:37:55 GMT
References: <8910261808.AA08540@expo.lcs.mit.edu>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 27


   From: kit@expo.lcs.mit.edu (Chris D. Peterson)
   Date: Thu, 26 Oct 89 14:08:39 -0400

   It seems to me that you don't want a shell at all, that what you
   really want is an unmanaged child of the application shell that
   contains your application.  If you do not mananage a child widget
   it will be ingored by its parent, and you will be able to move it
   around all you want with XtSetValues() on XtNx and XtNy.

   This solution should meet all of your criteria, and you don't have
   to deal with the window manager at all.

  Sigh.  There's one criterion I forgot about.  It's a wish, but not
a requirement; namely, I want to be able to use XtPopup and XtPopdown
on the widget, as well, as being able to use the MenuPopup and
MenuPopdown action procedures.  It is my understanding that you can
only use these functions with shells?

  If I have to, I'll write my own routines to pop up and pop down the
box (it's for an error message) and direct all keyboard input to it,
but doing an XtPopup is just so much easier :-).

Jonathan Kamens			              USnail:
MIT Project Athena				11 Ashford Terrace
jik@Athena.MIT.EDU				Allston, MA  02134
Office: 617-253-4261			      Home: 617-782-0710