Path: utzoo!attcan!uunet!samsung!sdd.hp.com!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!lll-winken!gauss.llnl.gov
From: casey@gauss.llnl.gov (Casey Leedom)
Newsgroups: comp.windows.x
Subject: mit/lib/Xaw/Imakefile and -DSHAPE: Command and Mailbox widgets
Message-ID: <61674@lll-winken.LLNL.GOV>
Date: 14 Jun 90 22:22:31 GMT
Sender: usenet@lll-winken.LLNL.GOV
Organization: Lawrence Livermore National Laboratory
Lines: 22


  Why do the Xaw Command and Mailbox widgets depend on a definition of
SHAPE?  The lib/Xaw/Imakefile adds -DSHAPE to the make macro DEFINES, so
they compile correctly in the source tree.  However, when 
<X11/Xaw/CommandP.h> or <X11/Xaw/MailboxP.h> are included by client
software, say to subclass the Command widget, SHAPE isn't typically
defined.  I have a friend who just spent an entire day trying to figure
out why his subclass of the Command widget wasn't working.

  Fundamentally, what I'm asking is: why bother with SHAPE ifdef's at
all?  I know for a fact that a client that uses the Command widget which
has been compiled with SHAPE defined will work against an R3 server
(without of course the shaped buttons, etc.)  The same goes for the
Mailbox widget.  So why do they need to have SHAPE ifdef's at all???

  At the very least, if it's absolutely necessary to use SHAPE ifdef's
for some reason, then SHAPE should be defined in some header file that
one can't get by without including, say <X11/X.h> or <X11/Xlib.h>.

  Would someone enlighten me on the issues here?  Thanks for your time.

Casey