Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!van-bc!jonh!jhenders From: jhenders@jonh.wimsey.bc.ca (John Henders) Newsgroups: comp.sys.atari.st.tech Subject: Re: MIDI (one problem solved?) Message-ID: Date: 18 Feb 91 03:23:00 GMT References: <1991Feb18.061505.7091@convex.com> <3998@ryn.mro4.dec.com> Reply-To: jhenders@jonh.wimsey.bc.ca Distribution: comp Lines: 21 X-Version: Martin's Mailer Version Sep 07 1990 23:50:52 In <1991Feb18.061505.7091@convex.com>, William Rosencranz writes: >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... > Kbdvbase() returns a pointer to a vector table pointing to routines to handle midivec,midi over-run error handling as well as other routines. All that needs to be deone is to replace the slow handler with your own fast code, and stuff a pointer into the vector table. -- John Henders jhenders@jonh.wimsey.bc.ca MIND over MIDI Productions or ubc.cs!van-bc!jonh!jhenders Vancouver,B.C