Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!uwvax!husc6!sri-unix!hplabs!hp-pcd!hpcvlo!ken From: ken@hpcvlo.UUCP Newsgroups: comp.windows.x Subject: Re: Uwm extensions, perhaps? Message-ID: <3940003@hpcvlo.HP.COM> Date: Tue, 24-Feb-87 13:03:10 EST Article-I.D.: hpcvlo.3940003 Posted: Tue Feb 24 13:03:10 1987 Date-Received: Fri, 27-Feb-87 21:27:48 EST References: <8702211303.AA01735@gjetost.wisc.edu> Organization: Hewlett-Packard Co., Corvallis, OR, USA Lines: 33 > Here's an example of the problem: Suppose I want to use the right > mouse button to raise windows. Then I can't use the right mouse button > to talk to any application, since uwm grabs it "first". Another fix is to make uwm obey it's own conventions. For example specify that an event should be handled by uwm in a root only context. Then have uwm respond to this event only when the mouse is over the root window, and let the other applications get this event first when the mouse is over their window. We made this change to uwm, and everyone in our area is running the modified uwm. It works fine. We added a total of 30 lines of code to uwm in scattered places. If anyone wants these changes I will be glad to submit them in some appropriate form to an appropriate place, (or perhaps set up an anonymous ftp?). For example here is an except from my .uwmrc file that allows me to use the left mouse button to circle_up windows, without stealing the left mouse button from application windows. With a slightly modified uwm the left mouse button as set here is context sensitive with respect to the mouse position. A left mouse button on the root window will circle up, and a left mouse button on an icon or window is ignored by uwm to be handled by the application. f.raise = meta : w|i :left down f.circleup = meta : r :left down f.moveopaque = meta : w|i :left delta f.iconify = meta : w|i :middle down f.circleup = : r :left down -Ken Bronstein hp-pcd!ken