Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ucbvax!ucbcad!faustus
From: faustus@ucbcad.UUCP
Newsgroups: comp.windows.x
Subject: Re: Window managers grabbing buttons
Message-ID: <1295@ucbcad.berkeley.edu>
Date: Wed, 4-Mar-87 20:00:22 EST
Article-I.D.: ucbcad.1295
Posted: Wed Mar  4 20:00:22 1987
Date-Received: Fri, 6-Mar-87 05:40:50 EST
References: <8702211303.AA01735@gjetost.wisc.edu> <1024@cartan.Berkeley.EDU> <8227@decwrl.DEC.COM>
Organization: CAD Group, U.C. Berkeley
Lines: 14

The solution that I used with an xterm that I wrote was to make the
mouse buttons configurable.  It is possible in the .Xdefaults file to
have an option of the form "xterm.Button.ShiftMetaLeft: Cut".  This way
you can distribute the functionality of your buttons any way you like.
It also makes it reasonable to have more functions than there are
button combinations for, and let the user pick the ones he wants.

Another possibility is to restrict the wm functions to certain
contexts.  For instance, an unshifted click inside an icon can always
mean "open".  For this to work the wm will have to be able to forward
events it doesn't need to the appropriate client, which may be a lot of
trouble and too much overhead...

	Wayne