Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!convex!rosenkra
From: rosenkra@convex.com (William Rosencranz)
Newsgroups: comp.sys.atari.st.tech
Subject: Re: MIDI (one problem solved!)
Message-ID: <1991Feb18.061505.7091@convex.com>
Date: 18 Feb 91 06:15:05 GMT
References: <3998@ryn.mro4.dec.com>
Sender: news@convex.com (news access account)
Organization: Convex Computer Corporation; Richardson, TX
Lines: 21
Nntp-Posting-Host: convex1.convex.com

In article <3998@ryn.mro4.dec.com> miskinis@aisg.enet.dec.com (John Miskinis) writes:
>	But, until I write code to handle the mouse and keyboard such that
>they behave correctly, I can't develop a nice user interface...

this may sound painfully simple (so simple it may not work - i have not
tried it), but maybe u could install your routine, so that is handles the
midi, then jumps to the old handler somehow. handle the midi yerself, let
the bios do its thing with mouse/keys/etc. you would need to "clear" any
midi event, so that the old handler never sees a midi event...

another idea is to disassemble the old code from memory loc u gave,
and fix it, calling it your own. or maybe just jump to the code which
does non-midi stuff.

am i nuts? (don't answer that :-)

-bill
rosenkra@convex.com
--
Bill Rosenkranz            |UUCP: {uunet,texsun}!convex!c1yankee!rosenkra
Convex Computer Corp.      |ARPA: rosenkra%c1yankee@convex.com