Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!hao!ames!elroy!cit-vax!ucla-cs!zen!ucbvax!atc.bendix.COM!Len%AIP1%TSD From: Len%AIP1%TSD@atc.bendix.COM Newsgroups: comp.windows.x Subject: Warping the Pointer for a Reconfigured Widget Message-ID: <8711241733.AA01132@ATHENA.MIT.EDU> Date: Tue, 24-Nov-87 09:20:00 EST Article-I.D.: ATHENA.8711241733.AA01132 Posted: Tue Nov 24 09:20:00 1987 Date-Received: Sat, 28-Nov-87 00:25:03 EST Sender: usenet@ucbvax.BERKELEY.EDU Organization: The ARPA Internet Lines: 22 Received: from GRACIE by HEART-OF-GOLD via CHAOS with CHAOS-MAIL id 503; Tue 24-Nov-87 10:16:44 EST Date: Tue, 24 Nov 87 10:16 EST From: Sai-Cheong Arnold Chu Subject: Warping the Pointer for a Reconfigured Widget To: "3077::in%\"xpert@athena.mit.edu\""@TSD1.ABATSD, gilgamesh@HEART-OF-GOLD.ABATSD Message-ID: <871124101645.4.GILGAMESH@GRACIE.ABATSD> Let me suggest that the source of this disagreement over whether to warp pointer or not is due to the double meaning of the cursor. Those who would like to see the cursor move with a widget is trying to preserve the context of the client behind the widget. Those who wishes the cursor to be stationary are trying to preserve the context of the whole screen. These are two distinct meanings for one cursor. Often, this is indicated by changing cursor shape when the cursor moves from a window to the background. To make explicit this distinction, I would advocate using separate cursors. One for overall interaction with the screen. One for each widget which needs locator input. Mouse input may be multiplexed between these separate cursor via keyboard modifier or commands. The focus of input may be indicated by blinking. This type of interaction is already present in systems with text cursors and mouse cursor. Implementation of this should be relatively straight forward.