Path: utzoo!attcan!uunet!husc6!uwvax!dogie!uwmcsd1!ig!agate!ucbvax!hplabs!hpda!hp-sde!hpfcdc!stroyan
From: stroyan@hpfcdc.HP.COM (Mike Stroyan)
Newsgroups: comp.windows.x
Subject: Re: Bugs in twm, wm, xprop, and xplaces (or my ignorance)
Message-ID: <6910001@hpfcdc.HP.COM>
Date: 19 Jun 88 01:40:31 GMT
References: <6562@jhunix.HCF.JHU.EDU>
Organization: HP Ft. Collins, Co.
Lines: 16

> That's because twm and wm don't set the class hints on the outer "frame"
> window they reparent your windows to. xprop/xplaces look at this frame window
> and see, of course, nothing.
> 
> 					Jordan

That's one way to look at it.  It seems to me that the problem is that
xprop/xplaces are just using the window id of the first child window
under root, as returned with the button event.  The programs could take
the screen coordinates of the button event and find the smallest window
by examining the window tree.  Xprop could report data on the smallest
subwindow or on that window and its ancestors.  That gives an xprop
user the power to indicate and get data about a window manager's border
area, or an application's window, or some subwindow.

Mike Stroyan