Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!husc6!think!ames!ucbcad!ucbvax!COGSCI.BERKELEY.EDU!bryce From: bryce@COGSCI.BERKELEY.EDU (Bryce Nesbitt) Newsgroups: comp.sys.amiga Subject: Re: Graphics tablets? Message-ID: <8707130043.AA11458@cogsci.berkeley.edu> Date: Sun, 12-Jul-87 20:43:00 EDT Article-I.D.: cogsci.8707130043.AA11458 Posted: Sun Jul 12 20:43:00 1987 Date-Received: Mon, 13-Jul-87 05:06:48 EDT Sender: daemon@ucbvax.BERKELEY.EDU Organization: University of California, Berkeley Lines: 23 Keywords: digitizers graphics tablets penmouse easel In article <1641@cadovax.UUCP> keithd@cadovax.UUCP (Keith Doyle) writes: < I've had a Summagraphics BitPad for quite a few years, it has a parallel < interface, and I'm sure I could figure out how to hook it up to the Amiga < parallel port. < [what do I do?] Hack up some hardware to convert the pad's parallel < port to mouse signals and hook it to the 9 pin (gag!)? Get out the < debugger and trap through DPaint (also gag!)? Pay EA $$$$$$ for < some kind of developers kit? Any suggestions? This is easy. Assuming you magically have the input from the tablet you simply format it like RAW mouse events, and call the input.device IND_WRITEVENT command. Dpaint will never know the difference. "poof" (See the Rom Kernal Manual's input.device chapter. Page 3-106) ----------------------------- |\ /| . Ack! (NAK, EOT, SOH) {O O} . ( " ) bryce@cogsci.berkeley.EDU -or- ucbvax!cogsci!bryce U "Success leads to stagnation; stagnation leads to failure."