Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!uwm.edu!linac!att!ucbvax!JESSICA.STANFORD.EDU!maas
From: maas@JESSICA.STANFORD.EDU
Newsgroups: comp.protocols.appletalk
Subject: Re: MacIP4.0 and Sys 7.0
Message-ID: <9105241658.AA12939@jessica.stanford.edu>
Date: 24 May 91 16:58:13 GMT
References: <675032483.5376040@AppleLink.Apple.COM>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 39


>In message <9105231318.AA00175@aquarium.ecn.purdue.edu>, moyman@ecn.purdue.edu
>(Mike Moya) writes:
>>Am I the only one that can't run an Apple menu item when MacIP is in the
>>forground??
> 
>No, but possibly you and I are the only two.  Actually, I've noticed this
>problem for quite a while now.  I'm not sure what's causing it, but it has
>persisted from version 2.1 up to version 4...
> 
>(Andy, are you listening?)

Yup, MacIP4.01 fixed the problem. For those who have SU-MacIP4.0
license and don't have MacIP4.01, drop me email and I'll send the
binhexed MacIP4.01 to you and your site contact person. It's not
available via anonymous FTP.

Using C call (Open (MPW C 2.0 ?) for opening Apple Menu item somehow
has such problem. And I don't think I did it the wrong way either.
Anyway, changing it to use Pascal call fixed it.

Here is the Pascal call version.

	if (theItem > SKIPAPPLE) {
		GetPort(&saveport);
		/* Aaron said C call version will bomb in System 7.0 */
		GETITEM(mainData.menu[menu_id(APPLEMENU)], theItem, deskname);
		OPENDESKACC(deskname);
		SetPort(saveport);
	}

> 
>--
>David Schlesinger (lefty@apple.com)    |    C:.M:.C:., D:.O:.D:.
>Apple Computer, Cupertino, CA          |
> 

Andy Maas
Stanford University