Path: utzoo!attcan!uunet!husc6!uwvax!tank!ncar!boulder!stan!garya
From: garya@stan.com (Gary Aitken)
Newsgroups: comp.windows.x
Subject: Re: PropertyNotify events
Message-ID: <316@stan.com>
Date: 19 Dec 88 21:15:27 GMT
References: <2133@daisy.UUCP>
Organization: Solbourne Computer Inc., Longmont, Co.
Lines: 13

In article <2133@daisy.UUCP>, klee@daisy.UUCP (Ken Lee) writes:
> ... our clients (and often the window manager) get swapped in to process
> the PropertyNotify when any property changes, even though most are not
> interested....  
> Is there any way to work around it?

One possible way around would be to have a single client serve as a
"property daemon", and send a ClientMessage event to the proper client.
The property daemon would be the only client selecting on property notify
(other than possibly the wm).

This would require that you establish some convention for informing the
property daemon of the client to be notified.