Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uunet!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!samsung!munnari.oz.au!murtoa.cs.mu.oz.au!rob
From: rob@cs.mu.oz.au (Robert Wallen)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Simulating a Menu Bar with Pop-Up Menus
Message-ID: <2884@murtoa.cs.mu.oz.au>
Date: 2 Dec 89 22:44:34 GMT
References: <9095@hoptoad.uucp> <1989Nov28.053644.28100@agate.berkeley.edu> <2880@murtoa.cs.mu.oz.au> <32943@ucbvax.BERKELEY.EDU>
Reply-To: rob@murtoa.UUCP (Robert Wallen)
Organization: Comp Sci, Melbourne Uni, Australia
Lines: 20

>I just checked THINK C V.4 for this. It crashed with a bus error.  

Hmmm.  Its been a while, but the last time I checked (may have been on a PLUS)
it just created a real small window which had a scroll up AND a scroll down
arrow and no entries ...

>It is undoubtedly a bug in Apple's code.

Yeh?  Why?  I mean sure the standard MDEF doesnt work quite the way I want it
to but I have never had it crash with bus errors or address errors...
Id blame Symantec before Apple on this one.

>On the other hand, my custom MDEFs have never had an problem with this.

My biggest object to writing my own MDEF (which is basically a copy of MDEF-0)
is that I cant track Apples changes to the system.  I dont have a color Mac
(just an SE/30 :-) and so its 'real hard' to make sure that my custom MDEF,
CDEF, etc handle all the appropriate 'mctb' thingies.  I would prefer to be
able to call the 'standard' code because I know (hope) that Apple will keep it
up to date for me.