Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!bu.edu!polygen!bill
From: bill@polygen.uucp (Bill Poitras)
Newsgroups: comp.windows.open-look
Subject: Re: an example of sticky windows in a .Xdefaults file for olvwm
Message-ID: <1086@redford.UUCP>
Date: 13 May 91 14:18:25 GMT
References: <1991May3.000802.29165@wlbr.imsd.contel.com> <1077@redford.UUCP> <1991May9.122751.2437@ssd.kodak.com>
Reply-To: bill@redford.UUCP (Bill Poitras(X258))
Organization: Polygen Corporation, Waltham, MA
Lines: 25

In article <1991May9.122751.2437@ssd.kodak.com> kcwong@ssd.kodak.com (K.C. Wong (253-7926)) writes:
>>Keep in mind that XView applications dont have the WM_CLASS property set,
>>so you can't add their names to the list.  I know, I have tryed it.
>>Personally I find this a major deficiency in XView apps.  Another minor
>>dificiency is the lack of session manger hints (WM_CLINT_MACHINE
>>WM_COMMAND).  While running XView apps, xlsclients (an X11R4 client)
>>doesn't report XView apps.
>>
>
>  Ok... how can we solve these problems if we write an Xview program?
>  Are there any way we can get a handle to the wmhints of a frame?
>
As long as you can get the Display and Window that corresponds the top
level frame, (sorry not an Xview programmer) you can set WM_CLASS with
XSetClassHInt (Section 10.2.1.5 of Xlib Programming Manual)
WM_CLIENT_MACHINE and WM_COMMAND with XSetWMClientMachine and XSetCommand
respectively.  Also check out the call to XSetWMProperties.  This will
allow you to set a whole slew of properties (including the ones already
mentioned) in one call.

+-----------------+---------------------------+-----------------------------+
| Bill Poitras    | Polygen Corporation       | {princeton mit-eddie        |
|     (bill)      | Waltham, MA USA           |  bu sunne}!polygen!bill     |
|                 | FAX (617)890-8694         | bill@polygen.com            |
+-----------------+---------------------------+-----------------------------+