Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.berkeley.edu.BERKELEY.EDU
Path: utzoo!decvax!decwrl!ucbvax.berkeley.edu!apollo
From: mike%bambi@MOUTON.ARPA
Newsgroups: mod.computers.apollo
Subject: smd_$set_tp_cursor and optical mice
Message-ID: <8601242146.AA21437@mouton.ARPA>
Date: Fri, 24-Jan-86 16:46:52 EST
Article-I.D.: mouton.8601242146.AA21437
Posted: Fri Jan 24 16:46:52 1986
Date-Received: Sat, 25-Jan-86 05:33:46 EST
Sender: daemon@ucbvax.berkeley.edu.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 13
Approved: apollo@yale-comix.arpa

I'm trying to write a program that listens to a Mouse Systems optical
mouse connected to my DN330's serial port and moves the DM cursor with
smd_$ calls.  The problem is this: the program correctly calls
smd_$stop_tp_cursor, but subsequent keystrokes (cursor keys, NEXT, etc.),
while moving the DM's idea of where the cursor is, DON'T actually move
the little blinking box.  Also, there doesn't seem to be any way to
query the system as to where the DM thinks the cursor is, so as to move
it to the correct place next time the mouse gets moved.

I've looked at the Bitpad example, and I think I'm doing the same thing
it is.  Does anybody have code to manage another locator device?

	- Mike