Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!ucsd!ucbvax!bloom-beacon!eng.sun.COM!smarks
From: smarks@eng.sun.COM (Stuart Marks, Four More Years!)
Newsgroups: comp.windows.x
Subject: Re: OpenWindows and WM_COMMAND?
Message-ID: <9010101928.AA05235@trantor.Eng.Sun.COM>
Date: 10 Oct 90 19:28:18 GMT
References: <546@spot.wbst128.xerox.com>
Sender: root@athena.mit.edu (Wizard A. Root)
Organization: The Internet
Lines: 22


XView programs don't initially set the WM_COMMAND property as is required
by the ICCCM.  This is a bug.  They do set this property in response to a
WM_SAVE_YOURSELF message, so sending this message works around the problem
effectively.  (All XView applications ask for WM_SAVE_YOURSELF.)

In any case, it's probably a good idea to send WM_SAVE_YOURSELF to those
clients who have requested it before you collect their WM_COMMAND
properties.  It will ensure that the command string is up to date.

On a related note, stan!ninja!toml@uunet.uu.net  (Tom LaStrange) writes:

> Speaking of WM_COMMAND, it sure would be nice if XView clients would also
> set WM_CLASS.  Anyone from Sun listening?

Yes I'm listening.  It is true that XView doesn't set WM_CLASS.  It should.

s'marks

Stuart W. Marks			ARPA: smarks@eng.sun.com
Windows & Graphics Software	UUCP: sun!smarks
Sun Microsystems, Inc.