Path: utzoo!attcan!uunet!nih-csl!lhc!ncifcrf!haven!udel!wuarchive!zaphod.mps.ohio-state.edu!rpi!bu.edu!dartvax!eleazar.dartmouth.edu!llama From: llama@eleazar.dartmouth.edu (Joe Francis) Newsgroups: comp.sys.mac.programmer Subject: Re: Mac IIsi Programmer's switch Message-ID: <25523@dartvax.Dartmouth.EDU> Date: 2 Nov 90 13:05:57 GMT References: <21461@well.sf.ca.us> Sender: news@dartvax.Dartmouth.EDU Distribution: comp Organization: Dartmouth College, Hanover, NH Lines: 18 In article <21461@well.sf.ca.us> David Phillip Oster writes: >The release notes for the IIsi say that you must hold down the key sequence >for at least 1 second to generate the NMI. Now that you know this, you >should find it more reliable. AAhhh! Oh well. This shoots the iisi for me. I'm a heavy user of macsbug (SADE can't tell me what my variables are half the time, and half of the rest of the time it can its wrong). It's so convenient to be able to click on your "Do something time intensive" button in your program and then break into macsbug, confident that you dont have to change the current heap to yours since multifinder doesn't get a chance to swap you out when your code is to busy to call WaitNextEvent. Having the NMI take 1 second shoots all of that. Probably just a minor anoyance to a few macsbug fans, but things like that really get me. ----------------------------------------------------------------------------- "The Switch is Dead: Long Live the Programmers Interrupt Switch" - JAF