Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!columbia!rutgers!sri-spam!ames!sdcsvax!ucbvax!audi.mit.EDU!ellis From: ellis@audi.mit.EDU (Ellis Cohen) Newsgroups: comp.windows.x Subject: Proposed Protocol Change to WarpPointer Message-ID: <8707301918.AA07785@audi.siemens.uucp> Date: Thu, 30-Jul-87 15:18:50 EDT Article-I.D.: audi.8707301918.AA07785 Posted: Thu Jul 30 15:18:50 1987 Date-Received: Sat, 1-Aug-87 10:48:56 EDT Sender: daemon@ucbvax.BERKELEY.EDU Distribution: world Organization: The ARPA Internet Lines: 33 PROPOSED PROTOCOL CHANGE TO WarpPointer Problem: WarpPointer provides only absolute warping, not relative warping. ------------------------------------------------------------ Consider an application where the user is moving the pointer around. When the user hits a key, the pointer must jump down 20 pixels. We tried to use WarpPointer (followed by XFlush, of course) but the effects were occasionally very distubing visually. The problem is that between the time the client receives the position at which the key press occured and then tells the server to WarpPointer twenty pixels below, the user may continue to move the pointer. Instead of smoothly jumping 20 pixels down from its current location, the pointer instead jumps twenty pixels down from where it was when the key press was received. ------------------------------------------------------------ Proposal: That the semantics of WarpPointer be modified slightly, so that if dst-window is None, then are taken to be relative to the current pointer position, providing a relative warp. Ellis Cohen Siemens RTL Tiled Window Project ellis.cohen@a.gp.cs.cmu.edu princeton!siemens!ellis (609) 734-6524