Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!uunet!mcsun!ukc!edcastle!lfcs!nick From: nick@lfcs.ed.ac.uk (Nick Rothwell) Newsgroups: comp.sys.mac.programmer Subject: Re: Debugging code that uses the MIDI Manager Message-ID: <4376@castle.ed.ac.uk> Date: 31 May 90 10:53:59 GMT References: Reply-To: nick@lfcs.ed.ac.uk (Nick Rothwell) Organization: Jenny Agutter Appreciation Society of Edinburgh Lines: 24 In-reply-to: schiff@birch.berkeley.edu (Michael Schiff) In article , schiff@birch (Michael Schiff) writes: >I've been trying to get started writing programs that use the MIDI manager (in >Think C 4.0), but I'm having lots of problems. I can't help you with your specific problem (I'm not using MIDIWakeUp), but can only give a general piece of advice: Keep the interrupt routines (read hooks and so on) as small and simple as possible. Don't ever try to do graphics and printing in them. Assigning global variables (after setting up A5) and calling some other MM routines (e.g. output) are OK things to do, but I wouldn't do anything else. These routines are running in deep space, and I'm not surprised you can't debug them. Hence: keep them small and simple, and do printing by running a global circular print buffer or something. Less chance to get them wrong this way. >Mike Nick. -- Nick Rothwell, Laboratory for Foundations of Computer Science, Edinburgh. nick@lfcs.ed.ac.uk !mcsun!ukc!lfcs!nick ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ Ich weiss jetzt was kein Engel weiss