Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!tut.cis.ohio-state.edu!ucsd!ucsdhub!hp-sdd!hp-pcd!hpcvlx!gabe
From: gabe@hpcvlx.cv.hp.com (Gabe Begeddov)
Newsgroups: comp.windows.x
Subject: Re: _MOTIF_WM_HINTS question
Message-ID: <100920144@hpcvlx.cv.hp.com>
Date: 28 Dec 89 23:09:27 GMT
References: <1989Dec21.182119.25973@Solbourne.COM>
Organization: Hewlett-Packard Co., Corvallis, OR, USA
Lines: 65


   / hpcvlx:comp.windows.x / toml@ninja.Solbourne.COM (Tom LaStrange) /  6:56 am  Dec 28, 1989 /
   I got zero, nada, none, zip, no responses to this note that I posted
   last week, other than the one saying that they would forward it to some OSF
   mailing list.  So I'll try again.  Any OSF people out there listening?

Would you believe a holiday backlog? No, well how about my mailer ate it? ...
   
   I have a couple of questions about the Motif _MOTIF_WM_HINTS property.
   
   1.  The definition of the property in the MWM programmers guide is 
       different from the definition in MwmUtil.h.  I assume the header
       file contains the proper definition:
Yes.   
       Is my assumption correct?  Are there any other differences between the
       documentation and the code that I should be aware of?  I can't UTSL,
       all I have are binaries and header files.

I have the code but can't find my documentation :-). 
	    
   2.  I only see this property set on transient windows and it never seems
       to make any sense.

The properties are only used (by an Xm client) when the related resources of 
VendorShell are set (XmNdecorations, XmNfunctions, XmNinputMode). This is 
done by default by dialogs (top-level subclasses of XmBulletinBoard) in order
to control whether a resize button is displayed (see XmNnoResize resource of
XmBulletinBoard). Fields that aren't set should have a value of -1 which is
only used for client side comparisons since Mwm first checks the flags field.

Mwm only honors settings in the property that are a subset of those specified
for the relavent Mwm resource. Client windows (top-level) and transient windows
(windows with a TRANSIENT_FOR property) use different resources i.e.
XmNclientDecorations and XmNtransientDecorations which also have different 
default value. These resources are MWM resources while the ones in the 
preceding paragraph are client side resources. See XmNVendorShell and the 
Motif Window Manager Configuration Guide for more information.
   
   3.  It might be nice if this property were placed on all windows that
       are created by the motif toolkit, not just windows that require
       different decorations.
   
This is a reasonable request. If you were a Motif source licensee you
could make a direct request for this kind of capability and also UTSL. 
   
   Thanks,
   Tom LaStrange

Happy Sylvester (aka New Year),

Gabe Beged-Dov
HP Interface Technology Operation